This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Can anybody please suggest me if Tomcat web server is enough for a web-app (JSP/Servlets) that has at least 300 concurrent users? If not, can you suggest me which of the commercially available java-enabled web servers (esp. with Servlet Containers but without EJB-support) can replace Tomcat and why?
I would appreciate, if you can let me know the comparison of standard web servers along with few parameters such as Performance, Concurrent Connections, Cost-effectiveness and so on.
Originally posted by William Brogden: Tomcat has no problem serving a moderate number of users - even with rather complex page generation, my on-line mock exam servlets handle most requests in less than 10 milliseconds. Bill
I have the same concern as Rao. How many concurrent users are considered "moderate"?
Author and all-around good cowpoke
Joined: Mar 22, 2000
"concurrent users" is really not the problem since servlets don't care how many people have a browser "pointed" at your server. The important figure is response speed under load of X requests handled per second. I have done load testing using fake loads created with HttpClient and also monitored real application response time histograms for servlet generated mock exams that do a lot of object creation and manipulation. With fairly cheap hardware, more than 50 requests per second would see a slowdown.
Searching for benchmarks, I turned up this recent article. in which Tomcat seems to show up well. Bill