Great analysis - I've been struggling with finding the right server to use for concurrency as I have very long-running requests to a third party API, and this looks like the right choice for us.
Re:Puma vs Phusion Passenger
by FooBarWidget on Thursday July 04, 2013 @10:36AM
(#5990795)
Thank you for that benchmark (even though it didn't cover Phusion Passenger Enterprise ;)
It looks very thorough.
Re:Puma vs Phusion Passenger
by jrochkind1 on Thursday July 04, 2013 @11:15AM
(#5990977)
Thanks. I am personally interested in Passenger and Passenger Enterprise -- I do run Passenger (free version) on several self-managed servers, and am happy with it.
There are two reasons I did not include Passenger Enterprise in my benchmarks:
1. As far as I know there is no way to run it on heroku. And I was intentionally benchmarking on heroku.
2. I wasn't going to pay for it just for the purpose of running benchmarks on it.
https://github.com/jrochkind/fake_work_app/blob/master/READM...
For some reason it didn't get much HN traction. But either it inspired these recent HN posts involving puma, or it's just a coincidence -- either way I'm glad to see puma getting more attention.
I think multi-threaded request dispatch (from either puma or passenger enterprise) are often the best way to maximize throughput in a web server with I/O-bound work, as the Java community has been doing for a while. Any implementation details are just minor tweaks compared to just doing multi-threaded concurrent request dispatch in the first place -- so it's no surprise to see Passenger Enterprise and puma performing similarly.
i agree with the Phusion essay, that Passenger currently has more robust admin/management/supervision features than puma. I hope puma continues to evolve, inspired by passenger
Although these features are not trivial to implement well -- I am very impresed by passenger's feature set, and very robust and reliable performance.
But if you want a free/open-source solution, or a solution that it makes sense to run on heroku -- puma is a (and the only) solid concurrent-request-dispatch solution already.