Some runtime controls for CGC #163
Merged
Conversation
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.
Adds three
@mpl ... --runtime settings for CGC:max-cc-depth: max depth allowed for a CGC. Default is3. Increasing this enlarges the scope of CGC, the impact of which is not clear yet. In general, we recommend keeping CGC shallow.cc-threshold-ratio: max allowable current-size/survived ratio for CGC. Default is2.0(very eager). Increasing this will increase space usage, and decrease the total amount of work performed by CGC.max-cc-chain-length: max number of simultaneous CGCs allowed per heap. Default2. The impact of this isn't clear yet (should do some experiments)