We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Analysis Summary
Worth Noting
Positive elements
- Provides a clear, quantifiable performance metric (70% faster allocation) comparing Ruby 3.4 and 3.5.
Be Aware
Cautionary elements
- The use of a specific micro-benchmark (instantiating a simple object 500,000 times) can be misleading if interpreted as a general application speedup.
Influence Dimensions
How are these scored?About this analysis
Knowing about these techniques makes them visible, not powerless. The ones that work best on you are the ones that match beliefs you already hold.
This analysis is a tool for your own thinking — what you do with it is up to you.
Transcript
I have a question for all of you. Do you allocate objects in your Rails app? Yeah. Object allocate. Yes. Let's cheer on object allocation. Woo. I love asking questions and I know the answer. Like, yes, we allocate. Woo. Allocations are much, much faster in Ruby 3.5. I hope is a good reason for all of you to upgrade. I want to show you a benchmark. We made them faster. Here's a benchmark. We have a user class here, and we're going to instantiate it 500,000 times. We actually made this 70% faster on Ruby 3.5 than it is in Ruby 3.4.
Video description
Do you allocate objects in your Rails app? (Trick question. Of course you do!) Ruby 4.0 is already live, but the previous version - Ruby 3.5 - already made object allocation much faster. In this benchmark, instantiating a simple User object 500,000 times is 70% faster compared to Ruby 3.4. Ruby maintainer and Rails Core member Aaron Patterson urges you to upgrade to the recent versions and make use of this performance boost. #Ruby #RubyOnRails #Performance #Programming #Rails #SoftwareEngineering