HPMAX returns the committed memory of the application and not the actual memory allocated

[GoogleCodeExporter]

HPMAX returns the committed memory of the application and not the actual memory allocated

[GoogleCodeExporter]

>HPMAX returns the committed memory of the application and not the actual 
memory allocated
I cannot reproduce this. If you use jconsole (memory-tab / heap / max-value), 
you'll see that it matches jvmtop.

I did some tests - in my environments HPMAX was always 10% below the -Xmx 
argument of the corresponding jvms.
If you double -Xmx value, you'll see that jvmtop will also double HPMAX.

You'll often see multiples of 455M values because often the maximum heap of 
jvms is defined as a multiple of 512M (implicitly or explicitly).
(I cannot explain the difference between 455M and 512M right now, however this 
is jvm implementation-specific).

Original comment by [email protected] on 18 Aug 2014 at 4:22