News for hackers. Stuff that matters.
Re:Puma vs Phusion Passenger by evanphx on Thursday July 04, 2013 @10:09PM (#5993191)
Yeah, you can certainly run puma in the same operational mode as unicorn with clustering. But what I'd suggest is that you do instead is creating 1.5 as many workers has you have cores in your machine and perhaps 8 threads per worker. With that configuration, you'll get much more even performance than unicorn because you won't get as much cpu thrashing from context switches between processes and the threads will allow a high number of concurrent requests to all make progress concurrently.
Re:Puma vs Phusion Passenger by FooBarWidget on Friday July 05, 2013 @04:55AM (#5994009)
Hi Evan, thanks for your great work on Puma. Back in the days Mongrel was already multithreaded but it never reached its full potential because multithreading in the Rails world was so messed up back then. I'm glad to see that you've developed it into such a good state. When I checked your code, it was simple, clean and easy to read. Wonderful technology.

Unicorn currently does have better fault-tolerance tools than Puma though, e.g. the 1-minute timeout on that Unicorn has by default. Unicorn also currently has more documentation than Puma. So there is a tradeoff in the choice, and there's still plenty that all the app servers can learn from each other.

Re:Puma vs Phusion Passenger by cmer on Friday July 05, 2013 @11:03AM (#5995142)
8 threads per worker on MRI? Isn't that a recipe for disaster? Or maybe I'm missing something?
Re:Puma vs Phusion Passenger by evanphx on Friday July 05, 2013 @11:05AM (#5995153)
Why would that be recipe for disaster? What do you think would happen?
Re:Puma vs Phusion Passenger by cmer on Friday July 05, 2013 @11:50AM (#5995376)
Aren't threads on MRI evil?
Re:Puma vs Phusion Passenger by evanphx on Saturday July 06, 2013 @12:10AM (#5997915)
No? I don't know what your referencing.