3 ms·

Since they left ruby (2.0) raw rails performance improved by 75% (3.0) https://www.fastruby.io/blog/assets/images/RRBPerfHistory_720.png https://www.fastruby.i

by elif 4y ago

Since they left ruby (2.0) raw rails performance improved by 75% (3.0) https://www.fastruby.io/blog/assets/images/RRBPerfHistory_720.png https://www.fastruby.io/blog/assets/images/RRBPerfHistory_72... Then in 3.2, ruby released YJIT which improved median rails response time by about 100% https://raw.githubusercontent.com/easydatawarehousing/ruby_measure_responsetime/main/data/rails_devise/plots/rails_devise_0_overview.png https://raw.githubusercontent.com/easydatawarehousing/ruby_m... It's kind of a golden era for rubyists that stuck it out. Beautiful maintainable code that hits C performance for many tasks.

Alifatisk 4y ago
"... hits C performance for many tasks" Really?
- elif 4y ago
  particular improvements that come closer to C are related to string operations and regex https://tomaszs2.medium.com/ruby-3-2-0-is-from-another-dimension-5249e3186ec9 https://tomaszs2.medium.com/ruby-3-2-0-is-from-another-dimen... here are some benchmarks from 2019 (ruby 2.5) related to string and regex operations. already certain operations were faster in ruby than C or go, particularly on longer strings. http://jultika.oulu.fi/files/nbnfioulu-202001201035.pdf http://jultika.oulu.fi/files/nbnfioulu-202001201035.pdf
  - Alifatisk 4y ago
    Wow
mrwnmonm 4y ago
Didn't know that, thanks for the update. Actually, now I want to give it a try, remembering my old romantic days.