What does it mean to scale to N number of users, where N is large? The answer is highly dependent on your benchmark, and in particular to the think time that your benchmark uses. It's very easy to scale to 16,000 users if they each make a request every 90 seconds: that's on the order of 180 requests/second... I'll explore some of the considerations you need to examine in order to benchmark a large system properly.The test involves scaling from 30 to 5000 concurrent users while monitoring system performance, error rates, and container initialization. In the end, there is no clear winner between Glassfish and Tomcat. How well either scales depends on configuration, environmental, load curve, and problem domain factors rather than the raw container implementation.
Scott Oak presents a good approach to testing container scalability in light of the ongoing debates about performance in the Glassfish and Tomcat containers. Performance measurements and results depend on what's being measured and how, as well as configuration. Scott's methodology is well thought out and the test results are enlightening rather than surprising. He wrote:
- Posted by: Eugene Ciurana
- Posted on: May 03 2007 07:13 EDT
- scalability to support ajax application by Hank Li on May 03 2007 23:46 EDT
- Re: Tomcat vs. Glassfish Redux: How to Test Container Scalabili by Reg Whitton on May 04 2007 08:14 EDT
ajax is popular now, so what would be the testing result on ajax field? One ajax model is that the client makes request every 5 seconds, the other model is comet. It would be interested to find data to compare both container in those two models. -Hank http://www.imhaha.com web-based MSN QQ IM.
... and what percentage of those N users :-) . double click every link? . click each link repeatedly when the server response starts to slow?