News for hackers. Stuff that matters.
Re:Benchmarking Ruby 2.6 to 3.2 by brigandish on Monday December 26, 2022 @08:55AM (#34137636)
If I'm reading those results right, it seems that Ruby was getting slower between 2.6.10 and 3.1.3 with yjit, and can still outperform Ruby 3+ versions without yjit. Does anyone know why this is?
Re:Benchmarking Ruby 2.6 to 3.2 by faraaz98 on Monday December 26, 2022 @09:03AM (#34137679)
I'd like to know this from a more informed person as well. My guess is that yjit is only now production ready, they've been building it for a while and enabled behind an experimental flag
Re:Benchmarking Ruby 2.6 to 3.2 by maxfurman on Monday December 26, 2022 @10:33AM (#34138371)
YJIT was disabled by default before 3.2
Re:Benchmarking Ruby 2.6 to 3.2 by gettalong on Monday December 26, 2022 @11:46AM (#34139289)
Yes, there was a bit of a drop off in performance but only when YJIT is not used. With YJIT there are performance gain. Also note that YJIT in 3.1 was still experimental and more proof-of-concept. Only with the 3.2 release was it now deemed production ready.

And YJIT's creator, Shopify, is already using it in production with Ruby 3.2 for all their store fronts!

Re:Benchmarking Ruby 2.6 to 3.2 by chucke on Monday December 26, 2022 @01:35PM (#34140378)
Small nitpick: Maxime Chevalier-Boisvert is the creator of YJIT and the BBV optimization technique that underpins it. Shopify is the company which employs her and funds its further improvement.
Re:Benchmarking Ruby 2.6 to 3.2 by gettalong on Monday December 26, 2022 @01:36PM (#34140392)
Yes, I know but thought it would be simpler to just say Shopify. Sorry for the inaccuracy.