New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ruby] Should we update the Rails/Ruby tests to use YJIT? #7106
Comments
I think there was a gap down for 3.3, when you compare https://web-frameworks-benchmark.netlify.app/result?f=rails-api,railsfor december 2023 and january 2024. Worth to investigate before enabling jit |
Maybe we should not @crimson-knight Let me explain ... Here is some figures
YJIT is a game changer, but not sure if this is our responsibility (I mean in this project) to override default. At least in Will it be the same for other, I do not kown |
I think it's a good idea to enable yjit by default. |
Since we recently got all of the Rails tests to run using the "optimized" production settings, should we also include YJIT to showcase the optimal Ruby configuration?
I think it would be interesting to see if it makes a difference.
The text was updated successfully, but these errors were encountered: