The JVM heap can be as large as you want it. But its up to existing
implementations on how well the gc implementation is and do you need that
much heap.
That being said - if your tomcat application runs fine under the current
memory limits - you are not adding more webapps (or or memory hogging items)
to it - there is no need to increase the heap. Let the OS use that memory for
other resources. Once the JVM grabs the memory - its taken an isn't given
back. (Unless newer jvms have become smarter to shrink the heap on demand)
-Tim
joon yoo wrote:
Hi,
Currently on our tomcat 5 server (1GB RAM, Win 2000 server SP4), we
have the "initial memory pool" and "max memory pool" values set to
768MB in the apache tomcat properties app.
The server is going to be upgraded to 2GB's of RAM, exactly what is
the limit of the amount of memory that can be allocated to tomcat and
still run stably?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
