Tracking size of the object that caused the collection

[Alex Aisinzon]

Hi all

 

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
collection.

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

 

Alex Aisinzon

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20090406/fec03ead/attachment.html