Always use fixed heap for NoGC - #113
Merged
Merged
Conversation
peterzhu2118
force-pushed
the
ruby-cpu-heap-no-nogc
branch
from
September 18, 2026 04:51
768d454 to
dcb68bc
Compare
Ruby and CPU heap doesn't make any sense when using the NoGC plan.
peterzhu2118
force-pushed
the
ruby-cpu-heap-no-nogc
branch
from
September 18, 2026 04:54
dcb68bc to
85f97bb
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ruby and CPU heap doesn't make any sense when using the NoGC plan.