Skip to content

Conversation

@tschatzl
Copy link
Contributor

@tschatzl tschatzl commented Oct 23, 2025

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 sequence 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


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8212084: G1: Implement UseGCOverheadLimit (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27950/head:pull/27950
$ git checkout pull/27950

Update a local copy of the PR:
$ git checkout pull/27950
$ git pull https://git.openjdk.org/jdk.git pull/27950/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27950

View PR using the GUI difftool:
$ git pr show -t 27950

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27950.diff

Using Webrev

Link to Webrev Comment

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
@bridgekeeper
Copy link

bridgekeeper bot commented Oct 23, 2025

👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Oct 23, 2025

@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:

8212084: G1: Implement UseGCOverheadLimit

Reviewed-by: ayang, iwalulya, fandreuzzi

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 master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot changed the title 8212084 8212084: Implement UseGCOverheadLimit for G1 Oct 23, 2025
@openjdk openjdk bot added the hotspot-gc hotspot-gc-dev@openjdk.org label Oct 23, 2025
@openjdk
Copy link

openjdk bot commented Oct 23, 2025

@tschatzl The following label will be automatically applied to this pull request:

  • hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@tschatzl tschatzl marked this pull request as ready for review October 23, 2025 09:02
@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 23, 2025
@mlbridge
Copy link

mlbridge bot commented Oct 23, 2025

Webrevs

@tschatzl tschatzl changed the title 8212084: Implement UseGCOverheadLimit for G1 8212084: G1: Implement UseGCOverheadLimit Oct 23, 2025
Copy link
Member

@walulyai walulyai left a 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
@tschatzl tschatzl requested review from fandreuz and walulyai October 23, 2025 11:47
Copy link
Member

@walulyai walulyai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 23, 2025
…ome unnecessary return

* better name for update_gc_overhead_limit_exceeded()
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Oct 23, 2025
@tschatzl
Copy link
Contributor Author

Also ran up to tier8 in our CI with no additional issues afaict.

@tschatzl tschatzl requested a review from albertnetymk October 24, 2025 05:25
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 24, 2025
@tschatzl
Copy link
Contributor Author

Thanks for all the reviews!
/integrate

@openjdk
Copy link

openjdk bot commented Oct 27, 2025

Going to push as commit 3d2ce80.
Since your change was applied there have been 32 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 27, 2025
@openjdk openjdk bot closed this Oct 27, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 27, 2025
@openjdk
Copy link

openjdk bot commented Oct 27, 2025

@tschatzl Pushed as commit 3d2ce80.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@tschatzl tschatzl deleted the submit/8212084-usegcoverheadlimit branch October 27, 2025 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

4 participants