Hi,
 
The other day Tomcat threw an OutOfMemoryException. This is our development version of 
Tomcat. Looking at the Windows processes revealed Tomcat at 158MB. I could not tell 
you whether that is a good or bad statistic for a 2 man development Tomcat that uses 
database pooling to SQL Server, Struts and a Content Management System. I don't 
consider what we are doing to be overly complicated. 
 
However, when we get to lauch to 300 people, I am a little nervous that we will hit 
OutOfMemory within seconds.
 
Our Tomcat 5 loads itself by default at around 30MB. When the first hit to the web 
application goes in it leaps by 2-3 MB. Then each subsequent request seems to cost 
about 50-100K for just moving around. There are not many session objects being stored. 
The memory increases all the time and very rarely drops. Last night when we left it 
stood at 70MB and coming in this morning it was still 70MB.
 
Would anyone be kind enough to provide some tips on how to analyse this problem or 
what it might be even with the view to a 300 user burdon being placed on Tomcat. Is 
Tomcat even supposed to be able to handle 300 users? Are there any good sources of 
information on the web relating to tuning Tomcat or its performance - I have looked 
around but could not find anything definitive. 
 
Many thanks for your time, ADC
 
 


<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> 
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com";>www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>

Reply via email to