RFR (S): 8022872: G1: Use correct GC cause for young GC triggered by humongous allocations
bengt.rutisson at oracle.com
Wed Aug 21 14:47:05 UTC 2013
Could I have a couple for reviews for this small change?
This change makes sure that we report "humongous allocation" as the GC
cause when we trigger a young collection because we are attempting a
Before the change a log entry for such a young GC looked like this:
[GC pause (G1 Evacuation Pause) (young) 1364M->1364M(2048M), 0.0004200 secs]
After the change it looks like this:
[GC pause (G1 Humongous Allocation) (young) 1364M->1364M(2047M),
While doing this change I realized that the GC cause
_g1_inc_collection_pause was only used in one more place. The slow path
for allocations. There is already a cause called _allocation_failure, so
I suggest that we use that one instead. This will eliminate the need for
In that case the webrev will look like this:
I prefer this cleanup, but I'm fine with just doing the first one if we
think _g1_inc_collection_pause cause to keep for some reason.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev