Ruby 3 Concurrency

on YouTube ↗42m

" summary

Proposal introduces a concrete concurrency abstraction named Guild membership model that pins mutable objects to one Guild, adds Guild::Channel with copy and transfer_membership move semantics, and describes an implementation trick (new headers + invalidation) to avoid copying big data. Author reports simulated runs in three languages where a Fibonacci master/worker on two cores beats single-Guild execution, but moving big arrays is currently slow. Implementation is unfinished; APIs and class/module sharing remain open problems.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 0:07Koichi Sasada Ruby 3 Concurrency
3. 2:14Replace Threads to Guilds
4. 2:57Kill Threads
5. 22:40We don't need to care about synchronizations any more Trade-off: Performance vs. Safety/Easily Which do you want to choose?

" related talks

• 39mParallel programming in Ruby3 with GuildKoichi Sasada · RubyConf 2018
• 40mRUBY 3.0 - SINGLE PROCESS, MULIPLE POSSIBILITIESMaciej Mensfeld · Grill.rb 2017
• 54mConcurrency: Rubies, pluralEleanor McHugh, Elise Huard · RubyConf 2010
• 38mModeling concurrency in Ruby and beyondIlya Grigorik · MountainWest RubyConf 2011
• 23mParallel Processing With RubyDilum Navanjana · RubyConf MY 2017
• 36mIntroduction to Concurrency in RubyThijs Cadier · RailsConf 2016
• 36mModern Concurrency Practices in RubyArnab Deka · RubyConf AU 2014
• 27mIn-Depth Ruby Concurrency: Navigating the Ruby concurrency landscapeJP Camara · RubyConf 2024