[Rivet] agile memory use

[Gavin Hesketh]

Hello,
Noticed this after seeing lots of batch job crashes. Sometimes I run 
agile with a large number of events (mostly because of the setup I have 
for alpgen). When this number gets very large, agile grabs a huge block 
of virtual memory before generating any events.
eg:
agile-runmc Pythia6:424 -n 10000000
grabs 170 MB

agile-runmc Pythia6:424 -n 100000000
grabs 1.5 GB, and tends to be killed by the batch queue I use.

x10 higher N won't initialise.

ok, 100M is a lot of events, and I've figured out a work-around for this 
in the way I run alpgen. But it seems strange that agile should be 
requesting so much memory when events are in the end fed to a pipe for 
rivet to read one by one. Is this expected? Seems to be independent of 
the generator I use.

thanks,
	Gavin