<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 01/15/13 05:55, Vitaly Davidovich wrote:
<blockquote
cite="mid:CAHjP37EhqMgGO+UzZk22YcETW8jatRt3nVVsya8yY6gR7b9J2g@mail.gmail.com"
type="cite">
<p dir="ltr">Hi Jon,</p>
<p dir="ltr">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?</p>
</blockquote>
<br>
Yes it does make sense. I'll add the checks and publish a new<br>
webrev. <br>
<br>
Thanks.<br>
<br>
Jon<br>
<blockquote
cite="mid:CAHjP37EhqMgGO+UzZk22YcETW8jatRt3nVVsya8yY6gR7b9J2g@mail.gmail.com"
type="cite">
<p dir="ltr">Thanks</p>
<p dir="ltr">Sent from my phone</p>
<div class="gmail_quote">On Jan 14, 2013 10:31 AM, "Jon Masamitsu"
<<a moz-do-not-send="true"
href="mailto:jon.masamitsu@oracle.com">jon.masamitsu@oracle.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
8005452: Create new flags for Metaspace resizing policy<br>
<br>
Previously the calculation of the metadata capacity at which<br>
to do a GC (high water mark, HWM) to recover<br>
unloaded classes used the MinHeapFreeRatio<br>
and MaxHeapFreeRatio to decide on the next HWM. That<br>
generally left an excessive amount of unused capacity for<br>
metadata. This change adds specific flags for metadata<br>
capacity with defaults more conservative in terms of<br>
unused capacity.<br>
<br>
Added an additional check for doing a GC before expanding<br>
the metadata capacity. Required adding a new parameter to<br>
get_new_chunk().<br>
<br>
Added some additional diagnostic prints.<br>
<br>
<a moz-do-not-send="true"
href="http://cr.openjdk.java.net/%7Ejmasa/8005452/webrev.00/"
target="_blank">http://cr.openjdk.java.net/~jmasa/8005452/webrev.00/</a><br>
<br>
Thanks.<br>
</blockquote>
</div>
</blockquote>
</body>
</html>