linuxhippy at gmail.com
Thu Mar 6 03:29:14 PST 2008
This is a bit off-topic ...
I think this switch is rather dangerous - some parts of the JDK rely
on explicit garbage collection (e.g. Direct-*Buffers, instances
pointing to non-heap memory cleaned up by finalizers). - the code
which is quite guaranteed to work is then lowered to "may work, may
fail", depending on the type of workload.
A API which would allow better control over the type of GC would be
quite helpful, as well as maybe a Hotspot-internal API which would
help controllnig native resources allocated outside the VM.
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
More information about the hotspot-gc-dev