-
Couldn't load subscription status.
- Fork 6.1k
8212084: G1: Implement UseGCOverheadLimit #27950
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
8212084: G1: Implement UseGCOverheadLimit #27950
Conversation
Hi all, please review these changes to implement the `UseGCOverheadLimit` functionality for G1 (and make the implementation for Parallel GC have similar output). The `UseGCOverheadLimit` feature prematurely returns `null` from a GC if GC cpu usage limits and heap usage limits are met for some time. This is to avoid a VM limping along if garbage collection gets into an endless cycle of garbage collections or until a "real" OOME is thrown. What is important here is how this works (derived from the Parallel GC implementation): * check overheads at the end of the (initial) garbage collection (before upgrading) to see whether we are over the limits for a successive amount of GCs. * keep doing GCs without actually allocating memory for the allocation request to keep on measuring gc CPU usage. This is important for measuring the correct cpu usage in case of the application being able to free memory on the OOME. Testing: tier1-5 without any OOMEs due to this feature, test case Thanks, Thomas
|
👋 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 22 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 |
Webrevs
|
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.
Some suggestions
* fandreuzzi review * some additional comment tweaks
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!
…ome unnecessary return * better name for update_gc_overhead_limit_exceeded()
|
Also ran up to tier8 in our CI with no additional issues afaict. |
|
Thanks for all the reviews! |
|
Going to push as commit 3d2ce80.
Your commit was automatically rebased without conflicts. |
Hi all,
please review these changes to implement the
UseGCOverheadLimitfunctionality for G1 (and make the implementation for Parallel GC have similar output).The
UseGCOverheadLimitfeature prematurely returnsnullfrom a GC if GC cpu usage limits and heap usage limits are met for some time. This is to avoid a VM limping along if garbage collection gets into an endless cycle of garbage collections or until a "real" OOME is thrown.What is important here is how this works (derived from the Parallel GC implementation):
Testing: tier1-5 without any OOMEs due to this feature, test case
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27950/head:pull/27950$ git checkout pull/27950Update a local copy of the PR:
$ git checkout pull/27950$ git pull https://git.openjdk.org/jdk.git pull/27950/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27950View PR using the GUI difftool:
$ git pr show -t 27950Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27950.diff
Using Webrev
Link to Webrev Comment