Conversation

Notices

1. Embed this notice
   Jeff McFadden (mcphat@ruby.social)'s status on Tuesday, 19-Sep-2023 01:11:33 JST Jeff McFadden

   We turned on yjit in production today and the results feel impossible.

   20-40% reduction in request times, with much less variability than we were seeing before.

   This is incredible.

   Between last week (Ruby 3.0) and this week (Ruby 3.2+yjit), our request times have been cut _in half_.

   • Embed this notice
     k0kubun (k0kubun@ruby.social)'s status on Tuesday, 19-Sep-2023 01:11:21 JST k0kubun

     in reply to

     • Joel Drapper

     @joeldrapper Did it speed up your specs as of 3.2? JIT is suitable for speeding up operations that are repeated many times like in production as you said. But tests often run each path a few times and that's it, so I normally don't expect a speedup there.

   • Embed this notice
     Joel Drapper (joeldrapper@ruby.social)'s status on Tuesday, 19-Sep-2023 01:11:22 JST Joel Drapper

     in reply to

     • Travis Bell

     @travisbell @mcphat I was trying 3.3 today and it doesn’t seem to have made any difference to the time it takes to run our specs, when compared to 3.2. I’m sure we’d see improvements in production though.

   • Embed this notice
     Travis Bell (travisbell@mastodon.social)'s status on Tuesday, 19-Sep-2023 01:11:26 JST Travis Bell

     in reply to

     • Joel Drapper

     @mcphat @joeldrapper I know right? It’s like pure magic. We saw a similar request time drop when we enabled it, ~30% or so.

     Can’t wait for the improvements in 3.3, it’s looking like we’re getting another solid bump in performance.

   • Embed this notice
     Joel Drapper (joeldrapper@ruby.social)'s status on Tuesday, 19-Sep-2023 01:39:44 JST Joel Drapper

     in reply to

     • k0kubun

     @k0kubun 3.2 with YJIT had made them faster in the past, but now it seems to make them slower. 🙃

     It makes sense because our tests repeat themselves a lot less now.