> That's 64 MB for the *Java heap*, not the entire process.
Thanks, that's what I didn't know.
--
Eric
Disclaimer - December 15, 2008
This email and any files transmitted with it are confidential and intended
solely for Tomcat Users List. If you are not the named addressee you should not
> From: Robinson, Eric [mailto:eric.robin...@psmnv.com]
> Subject: RE: Understanding Tomcat Memory Utilization
>
> Tomcat says it is configured to use a maximum of 64MB
That's 64 MB for the *Java heap*, not the entire process. The process space
includes lots of other things
> Welcome to paging.
I understand the difference between resident size and virtual image.
What I don't understand is why the tomcat status page indicates that
tomcat is configured to use a maximum of 64MB, but the resident size is
twice that and the virual image is four times that. In other word
> Welcome to paging.
I understand the difference between virtual image size and resident
size. The part I don't understand is the relationship between the tomcat
memory configuration as reported by the tomcat status page and the
actual usage as reported by top. Tomcat says it is configured to us
> From: Robinson, Eric [mailto:eric.robin...@psmnv.com]
> Subject: Understanding Tomcat Memory Utilization
>
> Can someone help me understand why tomcat is configured to
> use 64MB, but claims to peak at 48MB
Because that's all it needs to initialize. Unless you set -Xms == -
We have 60 instances of tomcat 5.X running on an RHEL4 server. Each instance
runs a copy of basically the same application, each for a different customer.
According to their respective status pages, the tomcats are all configured to
use a maximum of 64MB memory, but most peak at around 48MB.
