optcarrot
Async Ruby
optcarrot | Async Ruby | |
---|---|---|
5 | 20 | |
843 | 2,006 | |
- | 1.9% | |
0.0 | 8.0 | |
8 months ago | 4 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.
optcarrot
-
Is ruby really slow?
Here’s an NES emulator written entirely in Ruby. It’s a non-trivial exercise of performance and not something trivial/localize like running a loop a million times.
-
Concurrency in Ruby - how does it work?
a plot from the benchmark repo with versions listed
-
LOL, This is Ruby 3.0? 3x faster?
The goal was 3x performance from Ruby 2.0 to Ruby 3.0 on optcarrot not microbenchmarks. Work is now being done on microbenchmarks but optcarrot really did get 3x faster. https://github.com/mame/optcarrot#optcarrot-a-nes-emulator-for-ruby-benchmark
-
Why Wasn't Ruby 3 Faster?
For context the explicit stated goal as far as Ruby core is concerned is that https://github.com/mame/optcarrot/ will be 3x faster. This benchmark emulates NES in a headless environment and sees how many FPS it can generate. Which is a CPU heavy benchmark.
-
Artichoke is a Ruby Made with Rust that compiles to WebAssembly
I don't think it runs Optcarrot (the current most prominent Ruby benchmark) https://github.com/mame/optcarrot.
Async Ruby
-
EventMachine Performance Spikes
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
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?
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
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
-
Simple MapReduce that melt my brain (yes, fibers there)
For those who are interested here is the question.
- How does Ruby handle parallel HTTP requests in separate threads?
-
Two months into learning Ruby, it is the most beautiful language I ever learned
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?
In Github, there is a Async Gem(https://github.com/socketry/async).
- Efficient IO in Linux with io_uring [pdf]
What are some alternatives?
Smalltalk - Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
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.
artichoke - 💎 Artichoke is a Ruby made with Rust
EventMachine - EventMachine: fast, simple event-processing library for Ruby programs
Polyphony - Fine-grained concurrency for Ruby
Celluloid - Actor-based concurrent object framework for Ruby
Sequel - Sequel: The Database Toolkit for Ruby
net-ssh - Pure Ruby implementation of an SSH (protocol 2) client
render_async - render_async lets you include pages asynchronously with AJAX
ruby-mqtt - Pure Ruby gem that implements the MQTT protocol, a lightweight protocol for publish/subscribe messaging.
Ruby on Rails - Ruby on Rails
Opal-Async - Non-blocking tasks and enumerators for Opal.