Polyphony VS Async Ruby

Compare Polyphony vs Async Ruby and see what are their differences.

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
Polyphony Async Ruby
22 20
653 2,006
0.3% 1.9%
8.3 8.0
about 2 months ago 5 days ago
C Ruby
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Polyphony

Posts with mentions or reviews of Polyphony. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-10-16.
  • Should You Be Scared of Unix Signals?
    8 projects | news.ycombinator.com | 16 Oct 2023
    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

  • Polyphony 1.4 Released
    2 projects | /r/ruby | 2 Jul 2023
    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: Fine-Grained Concurrency for Ruby
    3 projects | news.ycombinator.com | 12 May 2023
  • Polyphony 0.99 released. Last release before 1.0!
    2 projects | /r/ruby | 9 Mar 2023
    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).
  • Polyphony – Fine-grained concurrency for Ruby
    1 project | news.ycombinator.com | 14 Nov 2021
  • About that monkey-patching business...
    1 project | dev.to | 4 Nov 2021
    Is monkey-patching inherently bad? Should its use make Polyphony illegitimate? These are the questions I'm exploring in my latest article.
  • Async Ruby
    7 projects | /r/ruby | 30 Oct 2021
    how is this diff from: https://github.com/digital-fabric/polyphony
  • Embracing Infinite Loops with Ruby and Polyphony
    1 project | dev.to | 13 Oct 2021
    Infinite loops are great for expressing long-running concurrent operations. In this article I’ll discuss the use of infinite loops as a major construct when writing concurrent apps in Ruby using Polyphony. I’ll show how infinite loops differ from normal, finite ones; how they can be used to express long-running tasks in a concurrent environment; and how they can be stopped. Read it now!
  • What's new in Polyphony and Tipi - August 2021 edition
    2 projects | dev.to | 27 Aug 2021
    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.
  • Sorbet Compiler: An experimental, ahead-of-time compiler for Ruby
    6 projects | news.ycombinator.com | 30 Jul 2021
    > 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

Async Ruby

Posts with mentions or reviews of Async Ruby. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-05.
  • EventMachine Performance Spikes
    2 projects | /r/ruby | 5 Sep 2023
    The Async gem is the natural successor, It's actively maintained, and allows you write synchronous code is if it wasn't non-blocking, and most libraries don't need any special support for Async (exceptions are gems with C extensions that do I/O and DB libraries with connection pooling that would otherwise be thread-based).
  • Philosophy of Coroutines
    7 projects | news.ycombinator.com | 1 Sep 2023
    https://github.com/socketry/async uses coroutines and I think in general it’s been a great model with very few downsides in practice.
  • Is ruby really slow?
    2 projects | /r/ruby | 21 Apr 2023
    There's async I/O. Here's a library that leans on Ruby 3's fiber scheduler.
  • Show HN: Goru, an experimental, Go-inspired concurrency library for Ruby
    2 projects | news.ycombinator.com | 3 Apr 2023
    Hey folks, wanted to show this off and get feedback. Still early/experimental but there are quite a few concepts I'm excited about here. This project came about while writing a program in Go and loving its approach to concurrency. Being a long-time Rubyist I immediately started to think about what similar concepts might look like in Ruby.

    I set out with two main design constraints:

    1. Lightweight: I didn't want routines to be backed by fibers or threads. Having been involved some in the async project (https://github.com/socketry/async), I had some experience using fibers for concurrency but was curious if they could be avoided.

    2. Explicitness: Routine behavior must be written to describe exactly how it is to behave. I always felt like concurrent code was hard to fully understand because of the indirection involved. On the spectrum between tedium and magical I wanted to err more on the side of tedium with Goru.

    Goru routines are just blocks that are called once for every tick of the reactor. It is up to the developer to implement behavior in terms of a state machine, where on each tick the routine takes some action and then updates the state of the routine for the next tick. This fulfills both design constraints:

    1. Because routines are just blocks, they weigh in at about ~345 bytes of memory overhead.

    2. Routine behavior is explicit because it is written as a state machine inside the block.

    Couple more features worth noting:

    * Goru includes channels for buffered reading/writing (similar to channels in Go).

    * Goru ships with primitives for non-blocking IO to easily build things like http servers.

    Curious your thoughts!

  • Twitter (re)Releases Recommendation Algorithm on GitHub
    12 projects | /r/programming | 31 Mar 2023
  • Simple MapReduce that melt my brain (yes, fibers there)
    3 projects | /r/ruby | 16 Mar 2023
    For those who are interested here is the question.
  • How does Ruby handle parallel HTTP requests in separate threads?
    3 projects | /r/ruby | 2 Mar 2023
  • Two months into learning Ruby, it is the most beautiful language I ever learned
    5 projects | /r/ruby | 25 Feb 2023
    Welcome! Ruby isn't exactly "dying", but the hype/popularity is definitely fading. This is primarily because Ruby is no longer "new", most of Ruby's popularity came from Rails, and now Rails is no longer the "new hotness". However, Ruby still has lots of awesome features and lots of awesome other libraries and frameworks, such as the new fancy irb gem that uses reline, nokogiri, chunky_png, the async gems, Dragon Ruby, SciRuby, Ronin, and the new Hanami web framework.
  • ruby has supported native async or not?
    1 project | /r/ruby | 6 Feb 2023
    In Github, there is a Async Gem(https://github.com/socketry/async).
  • Efficient IO in Linux with io_uring [pdf]
    5 projects | news.ycombinator.com | 16 Oct 2022

What are some alternatives?

When comparing Polyphony and Async Ruby you can also consider the following projects:

Concurrent Ruby - Modern concurrency tools including agents, futures, promises, thread pools, supervisors, and more. Inspired by Erlang, Clojure, Scala, Go, Java, JavaScript, and classic concurrency patterns.

EventMachine - EventMachine: fast, simple event-processing library for Ruby programs

Celluloid - Actor-based concurrent object framework for Ruby

render_async - render_async lets you include pages asynchronously with AJAX

Sequel - Sequel: The Database Toolkit for Ruby

Opal-Async - Non-blocking tasks and enumerators for Opal.

net-ssh - Pure Ruby implementation of an SSH (protocol 2) client

tipi - Tipi - the All-in-one Web Server for Ruby Apps