RFR(S): 8010738: G1: Output for full GCs with +PrintGCDetails should contain perm gen size/meta data change info

Srinivas Ramakrishna ysr1729 at gmail.com
Tue May 14 00:40:43 UTC 2013

Hi John --

On Mon, May 6, 2013 at 3:23 PM, John Cuthbertson
<john.cuthbertson at oracle.com> wrote:

>> 4.896: [Full GC (Allocation Failure) 512M->343M(512M), 4.3640117 secs]
>>    [Eden: 0.0B(25.0M)->0.0B(97.0M) Survivors: 0.0B->0.0B Heap:
>> 512.0M(512.0M)->343.3M(512.0M)], [Metaspace: 1611K->2433K(6448K)]
>>  [Times: user=5.13 sys=0.15, real=4.36 secs]
> The information that gets printed mirrors that of the other collectors.
> Here's parallel GC:
>> 33.245: [Full GC (Ergonomics) [PSYoungGen: 133632K->3423K(144640K)]
>> [ParOldGen: 348158K->348158K(348160K)] 481790K->351581K(492800K),
>> [Metaspace: 1612K->2433K(6448K)], 2.5788089 secs] [Times: user=9.96
>> sys=0.00, real=2.58 secs]
> The information that's printed is the amount of metaspace used before the
> GC, the capacity, and the amount of reserved space.

Do you know why the "used after" for the metadataspace increased after
the full gc?
Is that normal, common, rare or abnormal ? :-)

thanks John!
-- ramki

More information about the hotspot-gc-dev mailing list