Ruby 3.3 - Hackdot

Re:Ruby 3.3 by pdimitar on Monday December 25, 2023 @01:09PM (#38764692)

That is true, yes, but still comparing e.g. Rust vs. Ruby I'd think Rust spends anywhere from 10ns to 100ns (outside of waiting on DB) and Ruby no less than 10 ms. Still pretty significant and can add up during times of big load.

Also I remember Rails' ActiveRecord having some pretty egregious performance footprint (we're talking 10ms to 100ms on top of DB waiting) but I hear that was fixed a while ago.

[ Parent | on HN ]

Re:Ruby 3.3 by ajmurmann on Monday December 25, 2023 @02:44PM (#38765483)

My point was that if we look at Rails performance going up 10%, what does that mean for time spent in Ruby. I'd believe anything from a 15% to a 80% reduction of time spent in Ruby code

[ Parent | on HN ]

Re:Ruby 3.3 by pdimitar on Tuesday December 26, 2023 @05:27AM (#38770491)

I haven't seen 80% anywhere in the linked article[0] so let's use facts and not beliefs.

It is possible Ruby itself got accelerated a lot, okay, I am just not sure that's relevant since almost all Ruby usage is Rails.

[0] https://railsatscale.com/2023-09-18-ruby-3-3-s-yjit-runs-sho...

[ Parent | on HN ]

Re:Ruby 3.3 by ajmurmann on Tuesday December 26, 2023 @11:34AM (#38773225)

I wasn't trying to say that Ruby indeed is 80% faster, but that it's pretty much impossible to drive actual Ruby speed up from Rails numbers, since we don't know nearly enough about the Rails app

[ Parent | on HN ]