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 the other responses; allocating too much memory isn't a good
thing, either - so, if your app doesn't require the full 16GB, I would
keep Xmx at some lower limit (test with various Xmx settings, until
you find where the application behaviour starts to suffer from the lack
of memory -- then raise by some suitable amount).
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 (but
as there was a true leak, no amount of memory was enough). With this
bloater Xmx, when the memory became nearly full, the GC pause times
shot through the roof. With smaller Xmx, even though the memory became
full faster, the application also died more gracefully. With larger Xmx,
the application was for a long time in a "limbo" state; not serving,
but not dead, either.
--
..Juha
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
