Upgrade to Ruby 3.3 #984
Merged
Upgrade to Ruby 3.3 #984
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
acoffman
added
the
housekeeping
acoffman
force-pushed
the
ruby-upgrade
branch
from
a4ed4ae to
bb8d844
Compare
|
Additionally, updated our JSON serialization library, which claims about a 15% performance gain in the new version over the version we're using, and rolled everything out to staging. We are substantially behind on the graphql gem as well so I'm going to try to get that updated in this PR as well. |
|
Updated to the newest GraphQL libraries and rails version. Running successfully in staging. Will want to kick the tires some before rolling to prod. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are currently on 3.0 which is still receiving security updates for the time being, but will be EOL soon.
Ruby 3.3 (released in December) also comes with YJIT, which speeds up rails apps by somewhere between 15-20% in real world benchmarks (https://railsatscale.com/2023-12-04-ruby-3-3-s-yjit-faster-while-using-less-memory/). This adds an initializer which turns on YJIT if it's available.
Initially this will only swap staging to 3.3; if that goes well, we'll roll out to prod.