I love these write-ups. It’s so smart and forward-thinking to work on improving the performance of Ruby rather than investing exponentially more money and time into migrating to a more traditionally performant platform. Plus everyone gets the benefits. Their success has exceeded my wildest dreams of what might be possible to squeeze from Ruby in terms of performance.
The most exciting thing I got out of this is that Ruby 3.5 seems to have other memory optimizations as well - in the second graph, most benchmarks show an improvement from 3.3.6. Does anyone know what the specific optimizations are?
I love these write-ups. It’s so smart and forward-thinking to work on improving the performance of Ruby rather than investing exponentially more money and time into migrating to a more traditionally performant platform. Plus everyone gets the benefits. Their success has exceeded my wildest dreams of what might be possible to squeeze from Ruby in terms of performance.
The most exciting thing I got out of this is that Ruby 3.5 seems to have other memory optimizations as well - in the second graph, most benchmarks show an improvement from 3.3.6. Does anyone know what the specific optimizations are?
You have probably skipped over this section https://railsatscale.com/2025-01-10-yjit-3-4-even-faster-and-more-memory-efficient/#reduced-memory-usage . It contains a link to the corresponding change.
How stupid of me, thanks!