Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In this presentation titled "Ractor Reconsidered" at RubyKaigi 2023, Koichi Sasada discusses the current status of the Ractor system in Ruby, its challenges, and potential areas for improvement. Ractors were introduced in Ruby 3.0 to enable parallel computing, overcoming limitations posed by the Global VM Lock (GVL), which prevents threads from running in parallel. However, the adoption of Ractors has been slow due to several barriers. Key points include: - **Ractor System Purpose**: Ractors facilitate parallel programming by isolating object spaces, thus avoiding common issues related to mutable shared states. - **Performance Challenges**: The current performance of the Ractor system can diminish during garbage collection, where all Ractors are paused, causing overhead and latency. - **Knowledge Barrier**: The programming model required for efficient use of Ractors entails a level of understanding that isn't yet widespread. - **Implementation Quality**: The existing implementation of Ractors requires enhancements to ensure more robust and productive usage, as some complexities remain in the message passing API. - **Future Development**: Sasada emphasizes ongoing projects targeting improved garbage collection and more efficient native thread usage to boost the Ractor performance. In conclusion, while Ractors present a promising approach to concurrent programming, their current challenges necessitate community collaboration and strategic improvements to make them more viable and widely adopted within Ruby programming. Sasada invites participants to engage further in discussions during breaks, highlighting the importance of community contributions to the evolution of Ractor systems.
Suggest modifications
Cancel