Re: Generational GC: what to do when older generation overflows?

At 2006-05-24 08:30:34+0000, Ivan Boldyrev writes:

> When we collect objects from youngest generation into older one,
> unpleasant situation may happen: there is no more space in older
> generation but there are unprocessed objects in younger one.

I recommend that you design your system so that there is no fixed
limit on the size of a single generation.  Try to avoid having your
collection decisions for each generation forced on you by accidents of
survival rate, pigs-in-pythons, etc.

If you can't do this, arrange it so that you can insert and delete
extra generations.  I did this in the MLWorks garbage collector.  A
detailed description of the generation system in that collector can be
found in the list archives, for instance here:

<http://lists.tunes.org/archives/gclist/2001-October/002194.html>

Nick Barnes