request for review (s) - 8005452: Create new flags for Metaspace resizing policy
jesper.wilhelmsson at oracle.com
Mon Jan 28 15:08:59 UTC 2013
On 2013-01-26 00:50, Jon Masamitsu wrote:
> I've update the webrev2 (now 2 separate webrevs) for review comments.
> 8005452: NPG: Create new flags for Metaspace resizing policy
I have looked at the flag changes and they look good. I have a question
though. How do we want to handle the case where the user sets only
MinMetaspaceFreeRatio = 30 ? With your current change this will give an error
because the min is larger than the default max (20).
Would it make sense to assume that the user actually wants to use min=30 and
increase max to 30 as well? (or slightly more if they can't be equal) And
maybe issue a warning that the value of max has been changed.
The error would then just be given if the user specifies both flags and they
don't work out.
I'm not asking you to do this change now but it relates to other changes we
have done recently.
> 8006815: NPG: Trigger a GC for metadata collection just before the threshold
> is exceeded.
> On 1/16/2013 8:50 AM, Jon Masamitsu wrote:
>> I've added checks to arguments.cpp that are analogous to the
>> checks for MinHeapFreeRatio / MaxHeapFreeRatio
>> Changes since webrev.00 are in arguments.cpp
>> Thanks, Vitaly.
>> On 1/15/2013 5:55 AM, Vitaly Davidovich wrote:
>>> Hi Jon,
>>> Does it make sense to validate that the new flags are consistent (I.e. max
>>>> = min)? That is, if user changes one or both such that max< min, should
>>> VM report an error and not start?
>>> Sent from my phone
>>> On Jan 14, 2013 10:31 AM, "Jon Masamitsu"<jon.masamitsu at oracle.com> wrote:
>>>> 8005452: Create new flags for Metaspace resizing policy
>>>> Previously the calculation of the metadata capacity at which
>>>> to do a GC (high water mark, HWM) to recover
>>>> unloaded classes used the MinHeapFreeRatio
>>>> and MaxHeapFreeRatio to decide on the next HWM. That
>>>> generally left an excessive amount of unused capacity for
>>>> metadata. This change adds specific flags for metadata
>>>> capacity with defaults more conservative in terms of
>>>> unused capacity.
>>>> Added an additional check for doing a GC before expanding
>>>> the metadata capacity. Required adding a new parameter to
>>>> Added some additional diagnostic prints.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 236 bytes
Desc: not available
More information about the hotspot-gc-dev