Tracking size of the object that caused the collection

[Y.S.Ramakrishna at Sun.COM]

Unfortunately, there isn't such a flag at the moment, although
it would be very little work to add one.

You can surmise that a GC is occuring for a large object allocation request
based on how much of Eden is filled when the GC occurs, and whether
the old generation growth was abnormally large during that collection.
But these are of course approximate.

-- ramki

On 04/06/09 16:49, Alex Aisinzon wrote:
> 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
> 
>  
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use

_______________________________________________
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use