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.
This could be useful when triggering this at the end of initialization is efficient enough and it's more time-consuming to find a good
--yjit-exec-mem-size
that stabilizes Code GC.Railsbench stats
I checked the impact of calling the
RubyVM::YJIT.code_gc
atconfig/initializers/yjit_code_gc.rb
(last initializer):YJIT.code_gc
It seems like
config/initializers
is still too early for Code GC, but it's still better than never triggering Code GC.P.S. Looks like now
--yjit-exec-mem-size=9
is needed to fit all code today (it was 6 in #6406), maybe due to the reduced # of size exits (which is a good thing).