> 	...				    It can help prevent newspace
>     from growing so large (which is of course a big problem since it takes up
>     twice its usable space).
> 
> Interestingly, others have recommended just the opposite -- using a
> large newspace (as long as it is likely to fit well in physical
> memory).  Scavenging is quite fast, so it makes sense to use that
> phase of the GC as much as possible, as long as it doesn't thrash.

Which to try depends on whether you are allocating mostly temporary or
permanent data.  Anything that sticks around in newspace will
eventually be tenured, even if newspace is huge. If you find yourself
generating lots of temporary data, using destructive functions (as
recommended by the previous poster) is probably easier than tuning the
collector...

Good luck!


Wheeler
-- 
Wheeler Ruml, Aiken 220, <eecs.harvard.edu, at ruml> (617) 496-1066 (fax)
http://www.das.harvard.edu/users/students/Wheeler_Ruml/Wheeler_Ruml.html