Skip to content

Conversation

albertnetymk
Copy link
Member

@albertnetymk albertnetymk commented Sep 4, 2025

Remove a produce flag that controls maximum-compaction during a full-gc. The existing criteria, such as heap usage, old-gen density, are enough for deciding maximum-compaction.

Test: tier1-3


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
  • Change requires CSR request JDK-8366882 to be approved

Issues

  • JDK-8366881: Parallel: Obsolete HeapMaximumCompactionInterval (Enhancement - P4)
  • JDK-8366882: Parallel: Obsolete HeapMaximumCompactionInterval (CSR)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27091

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 4, 2025

👋 Welcome back ayang! 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 Sep 4, 2025

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

8366881: Parallel: Obsolete HeapMaximumCompactionInterval

Reviewed-by: iwalulya

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 6 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 8366881 8366881: Parallel: Obsolete HeapMaximumCompactionInterval Sep 4, 2025
@openjdk openjdk bot added the csr Pull request needs approved CSR before integration label Sep 4, 2025
@openjdk
Copy link

openjdk bot commented Sep 4, 2025

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

  • hotspot

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.

@openjdk openjdk bot added hotspot [email protected] rfr Pull request is ready for review labels Sep 4, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 4, 2025

Webrevs

@albertnetymk
Copy link
Member Author

/cc hotspot-gc

@openjdk
Copy link

openjdk bot commented Sep 4, 2025

@albertnetymk
The hotspot-gc label was successfully added.

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 ready Pull request is ready to be integrated and removed csr Pull request needs approved CSR before integration labels Sep 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot [email protected] hotspot-gc [email protected] ready Pull request is ready to be integrated rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

2 participants