Celluloid
Concurrent Ruby
Our great sponsors
| Celluloid | Concurrent Ruby | |
|---|---|---|
| 2 | 13 | |
| 3,884 | 5,536 | |
| -0.1% | 0.5% | |
| 0.0 | 0.0 | |
| 8 months ago | 21 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
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.
Celluloid
-
There are a *lot* of actor framework projects on Cargo.
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...
-
Best of (Ruby) Gems Series - What's Next? What's Hot?
Celluloid
Concurrent Ruby
-
Exploring concurrent rate limiters, mutexes, semaphores
After this, I took a look at the semaphore class in the popular library, concurrent-ruby to see how they implement it, and I learnt about something new: condition variables. And Ruby comes with this included!
-
Using Concurrent::Promise while rescuing exceptions in Ruby
As I could not find a clear example about how to rescue exceptions from Concurrent::Promises (part of the Concurrent Ruby gem ) I read through the documentation and here are two examples: one that documents success case and one that shows what is happening when there is an error.
-
Ask HN: Any efforts to remove the GIL for Ruby?
In a sense the GIL (or actually GVL as it's called in current ruby versions) has already been removed for ruby.
It's only the original MRI Ruby that still has it several over Ruby implementations already removed it. e.g. JRuby.
Concurrent-Ruby[1] is probably a good place to start if you want to work with GVL free ruby on JRuby. It's quite well supported and is currently used by Rails.
If you just want async or non-blocking IO I'd take a look at the Async Gem[2]. It looks pretty solid in Ruby > 3.0 and it's been invited by Matz to be part of the stdlib, which I think is a pretty good endorsement.
For MRI itself I don't think it's likely they'll ever remove the GVL. Ractors are probably a better solution for CPU concurrency in the long run, although I think they're pretty experimental currently.
-
Ruby 3.1.0 Released
I’d highly recommend the concurrent-ruby gem that has implementations of various metaphors of concurrency, from async to promises, as well as edge features such as actors.
-
The right way of parallelizing tasks in a Rails application
yes, but `Future` is being deprecated according to the docs. This syntax should possible with Promises (although on my library, it is not working as I expected, I need to look into it hahaha)
-
Best of (Ruby) Gems Series - What's Next? What's Hot?
Concurrent Ruby
-
What is the current state of event driven programming with fibers in ruby?
https://github.com/ruby-concurrency/concurrent-ruby seems to be the current king of concurrency in Ruby. A lot of different concurrency models are implemented so you can pick whichever makes the most sense for you. The downside is that since the library doesn't focus on one model over another, it's probably difficult to learn for beginners.
i think not: https://github.com/ruby-concurrency/concurrent-ruby/issues/899
What are some alternatives?
Async Ruby - An awesome asynchronous event-driven reactor for Ruby.
EventMachine - EventMachine: fast, simple event-processing library for Ruby programs
Polyphony - Fine-grained concurrency for Ruby
render_async - render_async lets you include pages asynchronously with AJAX
Sequel - Sequel: The Database Toolkit for Ruby
ruby-vips - Ruby extension for the libvips image processing library.
libev_scheduler - A libev-based fiber scheduler for Ruby 3.0
net-ssh - Pure Ruby implementation of an SSH (protocol 2) client