pitchfork

There are several options but Puma seems to be the most popular at the moment. A derivative of Unicorn named Pitchfork is also in the works from Shopify - https://github.com/Shopify/pitchfork

Depends what you are after and what you are constrained by. Some people might be struggling with memory usage and may not see it as worth it, but for others who may have some extra RAM sitting around, it might come as a free perf increase. As for memory usage, proper use of CoW can reduce it dramatically: https://github.com/Shopify/pitchfork/blob/master/benchmark/R...

No, what is new here is reforking see https://github.com/Shopify/pitchfork/blob/master/docs/REFORK...

I'm the author of the original 'refork' feature introduced to Puma a couple years ago [1], that served as an inspiration for this project. As I understand it, Pitchfork is an implementation of a reforking feature on top of Unicorn, a single-threaded multi-process Rack HTTP server. The general idea of 'reforking' is that in addition to pre-forking worker processes at initialization time, you re-fork them on an ongoing basis, in order to optimize copy-on-write efficiency across processes, especially for memory allocations that might happen after initialization. The Pitchfork author mentions sharing YJIT machine code as a particularly important use-case [2], one that has become relevant in recent Ruby releases. I never saw much interest in the concept when I originally introduced the reforking feature to Puma, and it remained a kind of inter