Come Discuss Ractors and Concurrency with 'The Dude'!
summary
Benchmarks show ractors delivering true parallelism in CRuby—4s vs 9.5s on a big-decimal multiply workload—while Ruby 4 still marks the Ractor API experimental. A homemade multiplayer server/game Trianko runs many ractors (UDP server, player handlers) and exposes repeated isolation errors: setting class instance vars, weakref access, non-sharable constants, and surprising restrictions on instance variables and Ractor.value semantics. Fixes include moving state into helper objects, ractorizing classes, and tools like the Schmacker coverage gem and Ractorize gem to adapt existing code.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:16Ractors vs threads
- 7:05Multiplayer game with Ractors
- 11:54Ractors isolation limits
- 18:36Message passing and gems
- 21:45Ractors gotchas
- 25:56Use Ractors?
- 27:01Closing
related talks
25mRactor Demonstration
30mRactor on Ruby 3.4
27mParallel testing with Ractors - Putting CPU's to work
35mConcurrency in Ruby: Threads, Fibers and Ractors Demystified
29mUsing Ractors and Making Ractors Usable
29mMillion-Agent Ruby: Ractor-Local GC in the Age of AI
54mConcurrency: Rubies, plural
36mModern Concurrency Practices in Ruby