RFR (S): 7057939 : jmap shows MaxNewSize=4GB when Java is using parallel collector
Thomas Schatzl
thomas.schatzl at oracle.com
Thu Apr 18 13:13:30 UTC 2013
Hi,
On Thu, 2013-04-18 at 02:33 +0800, Krystal Mok wrote:
> Hi Thomas,
>
> Could the same kind of update be done for OldSize and SurvivorRatio?
> For OldSize, if it's not explicitly set then it'll always show a
> default value which is like 5MB or something, regardless of the
> collector used.
Going with the naming convention, OldSize would show the initial old
generation size.
> For SurvivorRatio, when using UseParallelGC or UseParallelOldGC, if
> it's not explicitly set then InitialSurvivorRatio is the flag that
> actually takes effect. It's better if SurvivorRatio could be updated
> accordingly too.
I think all collectors show these problems, just like in the MaxNewSize
case.
I created a CR which will become available later at
http://bugs.sun.com/view_bug.do?bug_id=8012591 . It is a bit more
generic as it requests to look at the other flags directly printed by
jmap as well.
Hth,
Thomas
More information about the hotspot-gc-dev
mailing list