8293861: G1: Disable preventive GCs by default #1758
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not a clean backport due to neighboring changes in the same file. Patch is simple and manual fixes are trivial.
As mentioned in the JBS issue, preventive GCs has had issues on JDK 17. TrinoDB is impacted and recommends disabling preventive GCs in trinodb/trino#15380. We have seen internal applications that are affected by this issue as well.
GHA are full green. Locally run tier1 tests are all green.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1758/head:pull/1758
$ git checkout pull/1758
Update a local copy of the PR:
$ git checkout pull/1758
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1758/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1758
View PR using the GUI difftool:
$ git pr show -t 1758
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1758.diff
Webrev
Link to Webrev Comment