-
Notifications
You must be signed in to change notification settings - Fork 81
8365956: GenShen: Adaptive tenuring threshold algorithm may raise threshold prematurely #198
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
8365956: GenShen: Adaptive tenuring threshold algorithm may raise threshold prematurely #198
Conversation
…eshold prematurely Reviewed-by: kdnilsen, phh
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
@earthling-amzn This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 73 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
This backport pull request has now been updated with issue from the original commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't see any obvious conflicts. It's worth calling out what they are, the maintainers will want to know to help estimate risk. You'll need a risk evaluation.
|
/approval request This change fixes a subtle off-by-one error when Shenandoah's generational mode computes a new tenuring threshold. In some cases, this may result in the tenuring threshold being raised prematurely. This results in an accumulation of objects in the young generation that should have been tenured. This in turn erodes the benefits of the generational mode and causes unpredictable cycle times when the tenuring threshold is lowered and all of these objects are tenured. We have tested this fix in all jtreg tiers and various performance benchmarks. This change only affects the generational mode for Shenandoah. |
@earthling-amzn |
/integrate |
@earthling-amzn |
/sponsor |
Going to push as commit c66d45a.
Your commit was automatically rebased without conflicts. |
@shipilev @earthling-amzn Pushed as commit c66d45a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Not clean, but not especially difficult to resolve.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u.git pull/198/head:pull/198
$ git checkout pull/198
Update a local copy of the PR:
$ git checkout pull/198
$ git pull https://git.openjdk.org/jdk25u.git pull/198/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 198
View PR using the GUI difftool:
$ git pr show -t 198
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk25u/pull/198.diff
Using Webrev
Link to Webrev Comment