before you can answer that question, you need to know what the average and peak concurrent requests is. without that 300-400 concurrent users doesn't mean much.
If those 400 users hit the site once per minute average over 30 minutes, it would mean 12,000 requests in 30 minutes. Even if the user hits the site once every 30 seconds, that would only be double 24,000 requests in 30 minutes. if I naively divide that to get requests/second, I get roughly 14 concurrent requests per second. Put it another way, that is basically 4% of the users sending a request at the same time. I would suggest stress testing your application. It's probably a good idea to look at your production access logs and run some stats. that way you're using real data as the basis of your test. peter On Apr 7, 2005 12:59 AM, Shrikant Navelkar <[EMAIL PROTECTED]> wrote: > Hi, > > We are planning to deploy an application (JSP/Tomcat/Oracle) for 300-400 > concurrent users. The hardware is HP/True UNIX platform and it is very > powerful. Unfortunately we can not deploy the application in a phased > wise manner. > > Can somebody help us to understand : > 1. How scalable Tomcat is ? Are there sufficient examples of Tomcat for > 300 + users ? > 1. What are the tools available for scalability testing ? > 2. Any document describing performance tuning of Tomcat server > 3. Can we implement multiple tomcat instances on same server for better > performance ? > > Thanks in advance > > Shrikant > > --------------------------------------------------------------------- > 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]
