Jetty run's fine on low spec hardware. The Jetty site is currently getting slashdotted and it is frequently in the top 1% of sourceforge sites. OK yahoo.com it's not, but it runs on a 166MHz 486 with only 32MB of memory running red hat.
That machine is also running 3 other sites, is
mail hub and does nightly jetty builds.
But if somebody would like to donate a gun multi CPU machine to the Jetty project....
Firstly It is not strickly true to say that tomcat does not look for speed. If anything it is a poor reference implementatin because it is trying to be suitable for production.
Jetty has been developed mainly as an efficient HTTP/1.1 server. The Servlet container is secondary to providing correct and efficient service of the protocol.
Jetty has been focused on being embedable in your application, rather than being a stand alone application server. Hence it is widely deployed but with very low visability. I wrote jetty and I'm still surprized when I find the jetty.jar inside IBM tivolli or Sonic MQ!
Slashdot Mirror
That machine is also running 3 other sites, is mail hub and does nightly jetty builds.
But if somebody would like to donate a gun multi CPU machine to the Jetty project....
Jetty has been developed mainly as an efficient HTTP/1.1 server. The Servlet container is secondary to providing correct and efficient service of the protocol.
Jetty has been focused on being embedable in your application, rather than being a stand alone application server. Hence it is widely deployed but with very low visability. I wrote jetty and I'm still surprized when I find the jetty.jar inside IBM tivolli or Sonic MQ!
Jetty has also been integrated with the Jonas J2EE server.
- Sonic MQ
- Tivolli NetView from IBM
- Subscriber Edge Services platform from Cisco
- JBoss
- JXTA
There is high quality professional services and support available for it, plus a helpful community.