tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Spies <>
Subject Re: cpu 100% java
Date Wed, 02 Aug 2006 21:48:15 GMT
Damn copy and paste..... I've re-edited for the missing details below,  
my apologies.

Quoting Justin Spies <>:
> The VSIZE question--when the JVM starts, it places a hold on the
> memory it thinks is needed.  So if you allocate a maximum heap of
> 256MB + the permanent size of 128MB (which I realize you haven't set
> and I don't recall the default) + extra overhead memory =3D3D 469MB of
> VSIZE.  Note that the JVM needs memory, as Chris mentioned, of HEAP +
> To check memory usage, you'll want to add the following to your
> startup parameters (plus any others you want):
> -verbose:gc -Xloggc:/tmp/garbage.log -XX:+PrintGCTimeStamps -XX:PrintGCDetai=
> =3D
> ls

The above should read
-verbose:gc -Xloggc:/tmp/garbage.log -XX:+PrintGCTimeStamps -XX:PrintGCDetails


> Also note that the above instance is using much more REAL memory
> (88MB) than the first instance, but has much less total allocated
> memory (288MB).  It's highly likely that the application is defaulting
> to a heap size of something like or 9MB.

The above should read
... to a heap size of something like 64MB or 96MB...


This message was sent using IMP, the Internet Messaging Program.

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message