Not really. A JVM implementation could queue the extra heap memory to a swap
disk just like an OS can. But the performance tradeoffs are so bad - that
writing such a jvm would be a bad idea. ;)
-Tim
Bruno Georges wrote:
Hi Tim
Correct me if I am wrong, but there is a limit of 2GB in a 32bits
architecture .
With Best Regards
Bruno Georges
Glencore International AG
Tel. +41 41 709 3204
Fax +41 41 709 3000
----- Original Message -----
From: Tim Funk [EMAIL PROTECTED]
Sent: 05.12.2005 12:48
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: memory limit for tomcat?
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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
