Hi Guido, Usage of non blocking NIO in connectors such as Jetty tends to reduce the raw throughput but to increase the number of concurrent connections that can be handled. The best configuration really depends on your actual load.
The Grizzly connector still needs some work to be configurable and usable as a production alternative to Jetty. This is not an issue with Grizzly itself, more with our Restlet extension for Grizzly. Best regards, Jerome Louvel -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : weltermann17 [mailto:[email protected]] Envoyé : jeudi 25 mars 2010 12:34 À : [email protected] Objet : Re: Why is the default http server so much faster than Jetty and Grizzly? Reading the documentation as always helps: Switching the internal type for Jetty to BlockingChannelConnector (type=2) improves the performance dramatically: Results: troughput in megabytes per second (MB/sec) Internal/Default Jetty Grizzly localhost empty cache > 40 17 16 localhost from cache > 120 > 120 > 120 100mbit empty cache 10.8 10.9 0.5 100mibt from cache 10.7 9.8 11 Grizzly does not seem to be configurable in such an easy way, maybe somebody has an idea? Guido Schmidt -- View this message in context: http://n2.nabble.com/Why-is-the-default-http-server-so-much-faster-than-Jett y-and-Grizzly-tp4777255p4797065.html Sent from the Restlet Discuss mailing list archive at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=24648 56 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2593347
