This post was too unscientific and was updated. Jetty is an excellent container and the container of choice whenever I do something with servlets. Ever since weâ€™ve developed SnipSnap some years ago I love Jetty. Glassfish has some very promising features like the admin console and IÂ´m eager to try Glassfish in a project sometimes in the future.
Reading about another story of Rails performance, I grabbed JMeter to benchmark one of my current projects. Not so much as a comparison for Ruby – which managed 320 requests per second – but more as a comparison of Jetty and Glassfish.
Both servers were started with their default configuration through their maven plugins (wonderful easy to use
mvn glassfish:run). Unscientific as it may be, the numbers are:
- around 1000 requests/sec for both containers
Both with 200 threads and 50 requests per thread. Both numbers are great for my MacBookPro and good enough for me. They also are so close to each other so they are not a deciding factor for either Glassfish or Jetty. At the risk of comparing apples to oranges I have no fear of deploying this to a production system and scaling cheap (and even better with E-Tag caching), keeping in mind the requests per second with 25 servers in the Rails example.
Thanks for listening.
Update:: Another Rails application which thinks it did scale – at least with Merb, to 650k page views per day, well that’s “650K hits per day is ‘only’ around 8 per second (assumed a 20 hour day to spike it a little). This doesnt actual seem all that much?”.
The JMeter speed and 1000req/sec (for an admittantly simple REST GET) results in … 86.4M requests per day. Uh. On my MacBookPro.