4 ms·
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
by brigandish 4y ago
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?
- gettalong 4y agoYes, 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!
- chucke 4y agoSmall 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.
- gettalong 4y agoYes, I know but thought it would be simpler to just say Shopify. Sorry for the inaccuracy.
- faraaz98 4y agoI'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
- maxfurman 4y agoYJIT was disabled by default before 3.2