polyphony

When using green threads/fibers/coroutines, an interesting technique to make signal handling safer is to run the signal handler asynchronously on a separate fiber/green thread. That way most of the problems of dealing with signals go away, and there's basically no limitation on what you can do inside the signal handler. I've successfully used this technique in Polyphony [1], a fiber-based Ruby gem for writing concurrent programs. When a signal occurs, Polyphony creates a special-purpose fiber that runs the signal handling code. The fiber is put at the head of the run queue, and is resumed once the currently executed fiber yields control. [1] https://github.com/digital-fabric/polyphony

another cool ruby library for async is https://github.com/digital-fabric/polyphony

> Curious if there’s anything public about improving ruby performance from the I/O angle mentioned in the post. I'm currently working on Polyphony [0], a Ruby gem for writing highly-concurrent Ruby apps. It uses Ruby fibers under the hood, and does I/O using io_uring (on Linux, there is also a libev-based backend). [0] https://github.com/digital-fabric/polyphony

Ruby has fibers, though up until recently they weren't used much for anything, except lazy iteration. Recent efforts have built on fibers to provide concurrency with non-blocking I/O: https://github.com/socketry/async https://github.com/digital-fabric/polyphony Disclaimer: I'm the author of Polyphony.