Re: [Gc] GC code size
ivmai at mail.ru
Tue Mar 15 09:58:39 PST 2011
1. The recent doc says:
SMALL_CONFIG Tries to tune the collector for small heap sizes,
usually causing it to use less space in such situations. Incremental
collection no longer works in this case. Also, removes some
statistic-printing code. Turns off some optimization algorithms (like data
prefetching in the mark routine).
LARGE_CONFIG Tunes the collector for unusually large heaps.
Necessary for heaps larger than about 4 GiB on most (64-bit) machines.
Recommended for heaps larger than about 500 MiB. Not recommended for
embedded systems. Could be used in conjunction with SMALL_CONFIG to
generate smaller code (by disabling incremental collection support,
statistic printing and some optimization algorithms).
2. It's ok to define both SMALL/LARGE_CONFIG (at least with the recent snapshot).
Mon, 14 Mar 2011 19:24:03 +0100 Romano Tenca <rotenca at gmail.com>:
> Thanks Ivan, but i read:
> -DSMALL_CONFIG tries to tune the collector for small heap sizes,
> usually causing it to use less space in such situations
> Incremental collection no longer works in this case.
> -DLARGE_CONFIG tunes the collector for unusually large heaps.
> Necessary for heaps larger than about 500 MB on most machines.
> Recommended for heaps larger than about 64 MB.
> I need a>64 Mb heap. I think that 2 flags should be used: one to remove
> debug/print code, one to reduce heap size.
> Romano Paolo Tenca
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc