-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8295354: Remove G1 incremental non-copy time calculation #10987
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
8295354: Remove G1 incremental non-copy time calculation #10987
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 18 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 |
Thanks @walulyai @albertnetymk for your reviews |
Going to push as commit d634dde.
Your commit was automatically rebased without conflicts. |
Hi,
Currently G1 calculates the total non-copy time for young gen incrementally as regions are added to the young gen. The reason for this is that previously getting remembered set size has been expensive (i.e. part of non-copy time).
That is not the case any more since JDK 16 or so.
Further, actually in the calculation the remset work time does not need to be calculated on a per-region basis at all; first, it is incorrect as it does not remove duplicates, and additionally there is/has always been a total remembered set prediction anyway. (Which means the remembered set scan/merge time is considered multiple times).
So all this code can be removed.
Note that this change also fixes the same issue (double-counting of scan/merge time) for survivor regions.
Testing: tier1-3, manual testing wrt to pause time predictions which seem to be slightly better
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10987/head:pull/10987
$ git checkout pull/10987
Update a local copy of the PR:
$ git checkout pull/10987
$ git pull https://git.openjdk.org/jdk pull/10987/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10987
View PR using the GUI difftool:
$ git pr show -t 10987
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10987.diff