Puma: A Ruby Web Server Built For Concurrency

#1

Post by grk » Fri, Jan 06, 2012, 11:57 AM UTC

Puma: A Ruby Web Server Built For Concurrency
github.com

Re: Puma: A Ruby Web Server Built For Concurrency

#2

Post by jarito » Fri, Jan 06, 2012, 12:30 PM UTC

This seems like a neat accomplishment, but why would I use it? There is mountains of work for standard configurations including security hardening, monitoring, configuration management, etc.

What about this product makes it better than the other options?

Re: Puma: A Ruby Web Server Built For Concurrency

#3

Post by mbq » Fri, Jan 06, 2012, 12:56 PM UTC

tl;dr it parses HTTP headers with Ragel, which is a really nice idea; the state machine part is a yummy bite.

Re: Puma: A Ruby Web Server Built For Concurrency

#4

Post by juliennakache » Fri, Jan 06, 2012, 1:08 PM UTC

I'ven't looked at the code base, but I don't get how you're allowing true concurrency without any evented framework?

Re: Puma: A Ruby Web Server Built For Concurrency

#5

Post by mitchty » Fri, Jan 06, 2012, 1:18 PM UTC

juliennakache wrote: post #4

I'ven't looked at the code base, but I don't get how you're allowing true concurrency without any evented framework?

The same way every non-evented codebase does. Threads.

https://github.com/evanphx/puma/blob/master/lib/puma/thread_...

Re: Puma: A Ruby Web Server Built For Concurrency

#6

Post by moe » Fri, Jan 06, 2012, 1:19 PM UTC

If you want to claim it's fast ("screams") then you should provide some benchmarks.

Re: Puma: A Ruby Web Server Built For Concurrency

#7

Post by mattgreenrocks » Fri, Jan 06, 2012, 1:36 PM UTC

Puma uses a thread pool to handle requests. The only other Ruby web servers I know of that do this are Rainbows!, and Zbatery, and they're a bit obscure, unfortunately. Unlike Thin, EventMachine is not used.

I have it running on my Heroku instance for a day or so with no issues, though I don't get any traffic yet. :)

Re: Puma: A Ruby Web Server Built For Concurrency

#8

Post by juliennakache » Fri, Jan 06, 2012, 1:36 PM UTC

mitchty wrote: post #5

juliennakache wrote: post #4

I'ven't looked at the code base, but I don't get how you're allowing true concurrency without any evented framework?

The same way every non-evented codebase does. Threads. https://github.com/evanphx/puma/blob/master/lib/puma/thread_...

Then IMHO it's very unlikely to be "screamin" fast using the MRI

Re: Puma: A Ruby Web Server Built For Concurrency

#9

Post by dnc » Fri, Jan 06, 2012, 1:40 PM UTC

mbq wrote: post #3

tl;dr it parses HTTP headers with Ragel, which is a really nice idea; the state machine part is a yummy bite.

Correct me if I'm wrong, but I don't see how is this different from Thin, AFAIK it also uses Ragel for the same purpose.

Re: Puma: A Ruby Web Server Built For Concurrency

#10

Post by cies » Fri, Jan 06, 2012, 2:01 PM UTC

mattgreenrocks wrote: post #7

Puma uses a thread pool to handle requests. The only other Ruby web servers I know of that do this are Rainbows!, and Zbatery, and they're a bit obscure, unfortunately. Unlike Thin, EventMachine is not used. I have it running on my Heroku instance for a day or so with no issues, though I don't get any traffic yet. :)

if you need traffic the you forgot to put a url in your post.. :)