-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8295476: Split G1 cost per byte predictor on gc phase #10862
8295476: Split G1 cost per byte predictor on gc phase #10862
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
@tschatzl 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 59 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. ➡️ To integrate this PR with the above commit message to the |
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.
Lgtm!
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.
Looks good.
Thanks @albertnetymk @walulyai @kimbarrett for your reviews |
Going to push as commit 8de3eda.
Your commit was automatically rebased without conflicts. |
Hi,
please review this change to the cost-per-byte predictor to be split on gc phase (young-only/mixed) instead of during marking/outside of marking.
The reason is that the distinction between young-only/mixed of these values is higher than marking/outside of marking, although the latter degrades somewhat to the former in case of continuous concurrent marking where both are almost equivalent anyway. I believe that has been the original reason to do the marking/not-marking distinction.
I also removed the implied 10% extra cost for copies during marking (i.e. during the young-only phase). I could not find any particular reason why copying would be more expensive then with the current code base.
The distinction in general makes sense as the data copied during young-only and mixed is different (only short-lived data vs. short+long-lived data).
Testing: gha, examining predictions with some benchmarks
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10862/head:pull/10862
$ git checkout pull/10862
Update a local copy of the PR:
$ git checkout pull/10862
$ git pull https://git.openjdk.org/jdk pull/10862/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10862
View PR using the GUI difftool:
$ git pr show -t 10862
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10862.diff