Celluloid VS Polyphony

Speaking as someone who has used Erlang longer than most, who created a pre-Elixir-like language for Erlang's BEAM VM, and who routinely listens to Carl Hewitt's rants about why Erlang actors are bad, and who tried to make a Ruby actor library after using innumerable other library-level actor solutions...

Celluloid

Read the release notes here: https://github.com/orgs/digital-fabric/discussions/110 The Polyphony docs: https://www.rubydoc.info/gems/polyphony The Polyphony repository: https://github.com/digital-fabric/polyphony

Polyphony is a gem for building highly-concurrent Ruby programs. It utilizes Ruby fibers to provide a high-performance safe environment for launching any number of concurrent operations. Under the hood, Polyphony employs io_uring to maximize I/O performance (libev is used on platforms other than recent Linux kernels).

how is this diff from: https://github.com/digital-fabric/polyphony

Polyphony is a library for writing highly concurrent Ruby apps. Polyphony harnesses Ruby fibers and a powerful io_uring-based I/O runtime to provide a solid foundation for building high-performance concurrent Ruby apps.

> 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

Tipi is from https://github.com/digital-fabric/polyphony and also in the PR they add a gem: https://github.com/digital-fabric/libev_scheduler

Polyphony

There's the Polyphony project, which implements seamless concurrency on top of Ruby fibers. It's still not production-grade, but is used in production. Polyphony follows a different path in that it allows developers to continue using the Ruby core and stdlib APIs, and consequentially large parts of the Ruby ecosystem, in a multi-fiber environment. It puts a strong emphasis on structured concurrency, robust error handling and providing concurrency primitives that can be used to implement all kinds of concurrency patterns, such as actors (message passing between different fibers) and supervision trees.