My recent experience with tomcat 4.1.29 then 5.0.16 is that you have a few options you need to set to get the load up (see if these are applicable for your situation):

Spec: P4 2.7gig, 1gig RAM, SuSE 9.

In server.xml, look at updating the following attrs for your Connector:

maxThreads
minSpareThreads
maxSpareThreads
acceptCount

Also for catalina.sh/startup.sh, you need to look at passing some JVM settings, specifically:
initial heap size (-Xms)
max heap size (-Xmx)
thread stack (-Xss)


I found as I went along that I would get OutOfMemory, so I'd up the available heap. Then I got max number of threads has been reached, up threads to a realistic figure. Then the number of connections was limited.

acceptCount is quite important - I think it's the number of threads tomcat keeps waiting until the current thread count normalises - This was 100 by default, and on load tests I'd get just above 100 users hitting the system before it seemed to pause and not allow any more users. acceptCount fixed that.

For tomcat I found quite different performance when playing with all the above settings. One point is the thread stack size - I found it seemed to work best around 92k for one of my apps, but another required more.

When doing load tests, if you hit a wall try jProfiler to see what's going on.

Pete.






Gurlal Brar wrote:


Hi Tim,
Thanks for the reply.
Our server machine configuration is :
PIII 450MHz,256MBRAM,40 GB Harddisk.
Tomcat version : 4.0.4
JDK Version : 1.4 Network: Ping time is less than 10ms from load test client machine.
Server serves the sigle request in 5-10 seconds.


Test: We are trying to simulate 500-2000 users concurrently.


Is server with above configuration can hadle this load?
Some of the client requests are failing to open a socket with server
with the load of just 250 requests?Any clues why?


Thanks and regards
Gurlal Brar



-----Original Message-----
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 5:36 PM
To: Tomcat Users List
Subject: Re: Concurrent Requests


Tomcat can handle as many concurrent requests as the server it is on and the


speed of the network. Thats all the more specific I can be. There are too many variables in play. For example - the default servlet on a low powered box can easily serve 100 concurrent requests.

-Tim

Gurlal Brar wrote:



Hi All,
       I would like to know that how many concurrent requests to a single
Servlet Tomcat 4 can handle easily.
Please also refer some study material to do load testing of an web
application running in tomact 4.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








***********************************************************************************
This email and any files transmitted with it are confidential and intended solely for 
the use of the individual or entity to whom they are addressed. If you have received 
this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by MIMEsweeper for 
the presence of computer viruses.
***********************************************************************************
For any information on the Quinn Group of Companies please visit :-

http://www.quinn-group.com


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to