Re: Generational GC Automatic Heap Sizing : Runtime parameters

Hi,

GGC has been merged into stating.  Please test on some bigger programs
(than HelloWorld) and let us know how it went.

Congratulations Carl :)

				Grzegorz B. Prokopski

On Sun, 2004-10-03 at 20:41, Carl Lebsack wrote:
> I checked in my changes to allow the heap to size itself in the same 
> manner for GGC as the original copying collector.  The tag is:
> 
> /sablevm/developers/lebsack/svm-ggc-automatic-heap
> 
> I made modifications such that the heap parameters are identical to that 
> of the copying collector, and have the same meanings.
> 
> sablevm.heap.size.min
> sablevm.heap.size.max
> sablevm.heap.size.increment
> 
> For GGC there is only one additional parameter that can be set.
> 
> sablevm.heap.size.nursery
> 
> This is the nursery size (obviously) and defaults to 1MB.  I have also 
> added a special case such that if this parameter is set to 0, the 
> collector behaves as the original semi-space copying collector (Runtime 
> selection ;) ).  I believe this to be a better solution than actually 
> compiling both collectors into the library and will produce equivalent 
> behavior.  There is the slight added overhead of the write barrier still 
> present for the semi-space case, but that will always be the case with a 
> runtime selection.
> 
> This tag still requires ./configure --with-gc=gencopy to enable GGC.
> 
> Feedback/Questions welcome.


-- 
Grzegorz B. Prokopski      <[email protected]>
Debian GNU/Linux           http://www.debian.org
SableVM - LGPL'ed Java VM  http://www.sablevm.org
Why SableVM ?!?            http://sablevm.org/wiki/Features