RFR: 8035667: EventMetaspaceSummary doesn't report committed Metaspace memory

Erik Helin erik.helin at oracle.com
Tue Apr 1 15:23:17 UTC 2014


On 2014-03-28 16:03, Stefan Karlsson wrote:
>
> On 2014-03-28 15:52, Erik Helin wrote:
>> Hi all,
>>
>> this small patch makes the the trace event
>> vm/gc/heap/metaspace_summary report the amount of committed memory
>> instead of capacity. In the metaspace code, committed is used in all
>> places except one (and that will soon change) when making decisions
>> about sizing etc, therefore it makes much more sense that the trace
>> event reports the amount of committed memory.
>>
>> Webrev:
>> http://cr.openjdk.java.net/~ehelin/8035667/webrev.00/
>
> Looks good.

Thanks!
Erik

> thanks,
> StefanK
>>
>> Testing:
>> - Running JTREG JFR tests.
>>
>> Thanks,
>> Erik
>



More information about the hotspot-gc-dev mailing list