#4 new
liam

babble httpserver fails higher concurrency tests

Reported by liam | February 19th, 2009 @ 05:46 PM

Doing some very general, rough stress tests of the babble httpserver with ab, I observed consistent failures as the concurrency settings were increased.

From a recent (2/19/09) babble trunk install with the sample-student demo app, just blasting the front page reproduces the errors.

ab -n 10000 -c 50 http://127.0.0.1:8080/

works just fine, but

ab -n 10000 -c 100 http://127.0.0.1:8080/

results in a "Connection reset by peer" error in ab, which quits without finishing the rest of the tests.

Comments and changes to this ticket

  • liam

    liam February 26th, 2009 @ 05:28 PM

    It might be nice to leverage Grizzly (https://grizzly.dev.java.net) at the very least for an NIO framework and possibly as the guts of the http server as well. This is mostly pretty baseline stuff that, as far as I can tell, the current Babble implementation does not significantly differ from. The Grizzly web server is pretty small (800K), has very nice performance numbers, is well unit tested, is in production in a variety of projects, etc. It also has support for some of the fancier http features like Comet, in the event that becomes interesting to support in Babble.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Babble application server

People watching this ticket

Pages