search

laghdaf / jvmtop

Automatically exported from code.google.com/p/jvmtop
0 stars 0 forks source link

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

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
HPMAX returns the committed memory of the application and not the actual memory 
allocated. For example if my application is given 1024mb space then the HPMAX 
should return this value, but the HPMAX shows the committed memory for the 
application which is often a multiple of 455. Can someone please respond to 
this. Thanks you

Original issue reported on code.google.com by vmur...@uic.edu on 12 Aug 2014 at 9:07

GoogleCodeExporter commented 9 years ago 
>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 patric.r...@gmail.com on 18 Aug 2014 at 4:22