-
Notifications
You must be signed in to change notification settings - Fork 106
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
8314573: G1: Heap resizing at Remark does not take existing eden regions into account #429
Conversation
👋 Welcome back lmao! A progress list of the required criteria for merging this PR into |
@mmyxym 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 121 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. ➡️ 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. |
|
/approval request Clean backport of fix of G1 Heap resizing heuristics at remark. Risk is low which only affects the heuristics. |
Hi @mmyxym, I don't think the risk is that low. |
@GoeLin ,@jerboaa,I have noticed the original issue that heap resizing counted eden region size since the original JEP346 arrived in JDK12. The heap resizing heuristics in G1 remark Pause is similar to the one in Full GC which will estimate the heap capacity based on live set size. But counting of eden region size as part of live set will make the resizing behavior unexpected due to random eden use at remark pause . Only counting old objects as live set is more reasonable. As @tschatzl described in JDK-8315866, the behavior is expected which uses less memory for more gc activity. |
/integrate |
Hi, could any committers help with the integration? Thanks. |
/sponsor |
Going to push as commit 93d091a.
Your commit was automatically rebased without conflicts. |
@zhengyu123 @mmyxym Pushed as commit 93d091a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Clean backport of fix of G1 Heap resizing heuristics at remark
Additional testing:
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/429/head:pull/429
$ git checkout pull/429
Update a local copy of the PR:
$ git checkout pull/429
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/429/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 429
View PR using the GUI difftool:
$ git pr show -t 429
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/429.diff
Webrev
Link to Webrev Comment