@tenderlove Pitchfork/Unicorn does that by default.

Not to game any benchmarks though, but to check the client is still there.

@tenderlove yeah but right now the `.new` call as some allocation overhead because it takes keyword arguments. Your patch should eliminate that.

@tenderlove they are not that rare really. And in go to great length in Rails to not use `...` when possible in `Module#delegate`.

I'd love to burn all this if your patch makes it.

@tenderlove they are not that rare really. And in go to great length in Rails to not use `...` when possible in `Module#delegate`.

I'd love to burn all this if your patch makes it.

@tenderlove they are not that rare really. And in go to great length in Rails to not use `...` when possible in `Module#delegate`.

I'd love to burn all this if your patch makes it.

@tenderlove

@tenderlove I hear it's all the ragel

@nateberkopec The problem I see with this is that if the request allocates a lot, it might need to trigger it synchronously anyway.

I think I'd prefer a way to tell if we're close to need one or not, which is more or less https://github.com/ruby/ruby/pull/6791 (I need to dig into that one more)

@nateberkopec

Nit: it's actually `RUBYOPT='--yjit'` or ENABLE_YJIT=1