Tracking size of the object that caused the collection
aaisinzon at guidewire.com
Mon Apr 6 16:49:30 PDT 2009
We have historically seen performance degradation when large Java
Objects were allocated.
We came to this conclusion after reviewing some logs provided with
another JVM that trace the size of the object that triggered the
Is there a flag that can be set to allow tracing the size of the object
whose allocation triggered the garbage collection?
Our current target would be Sun JDK 1.5.
Thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-use