We have a driver that needs to do a bunch of work on a periodic basis.
We've built a job to kick this off by submitting triggers for members
of a dynamic group. Each event submitted is handled individually, so
memory requirements are low for the driver policy to actually execute
the work. But we would like to better understand the memory use of
the job itself. If the job is querying a dynamic group for its
200,000 members, is it trying to hold the entire result in memory as
one event and then generate the individual events into the driver
cache one at a time? Or is it processing each returned member one at
a time and not trying to hold them all in memory at once?

Anyone know?

Luke

--
I'm trying a new usenet client for Mac, Nemo OS X.
You can download it at http://www.malcom-mac.com/nemo