Julio Cesar Leiva wrote:
We have an app on a m linux box dual processor dual core , 16GB RAM
We are wondering what could be the ideal size for Xmx and Xms (Java Heap
Size)
We have a load test that hits our server with 800 clients sending
request every sec.
Thanks for your tips.
Adding to
From: Juha Laiho [mailto:[EMAIL PROTECTED]
Subject: Re: Xmx and Xms size
This recommendation comes from seeing (albeit with a now
obsolete JVM) excessively long pauses for GC in a situation
where an application with memory leak had gradually been
given higher and higher Xmx values
The answer is in the question, use the results of your load test to find
optimal values for you.
En l'instant précis du 30/01/08 15:19, Julio Cesar Leiva s'exprimait en
ces termes:
Hi all
We have an app on a m linux box dual processor dual core , 16GB RAM
We are wondering what could be the
What kind of processors specifically? In a 32-bit address space,
there's no point in giving Tomcat more than 2GB, because the JVM won't
use it. If you have 64-bit userspace and a JVM built for it then you
can use more, but remember to leave a bit for OS caches, other
processes, etc. (Starve the
From: Julio Cesar Leiva [mailto:[EMAIL PROTECTED]
We have an app on a m linux box dual processor dual core , 16GB RAM
We are wondering what could be the ideal size for Xmx and Xms
It is impossible to answer that question without detailed results from
stress-testing your application with a
Ah, yes, I addressed only -Xmx. For -Xms, you could try this. Throw
a typical load at your app. and monitor it until memory use seems to
be fairly stable. Round that up to a convenient number and use that
for -Xms. That way, your app. should not have to ask for more until
the load goes above
Thanks all of you for your tips.
They have gave us a lot of indication how to tackle this..
Great.,,,
Mark H. Wood wrote:
What kind of processors specifically? In a 32-bit address space,
there's no point in giving Tomcat more than 2GB, because the JVM won't
use it. If you have 64-bit
