8271064: ZGC several jvm08 perf regressions after JDK-8268372

[fisk]

After the integration of ZGC dynamic thread selection, there was a regression that popped up on a few benchmarks that all had in common a high allocation rate and very quick GC times. An extra conservative measure for not trusting the heuristics when using few GC threads, did not play very well with this scenario. The effect of it is back-to-back GC causing thousands of GCs when <100 were really needed. Removing this conservative measure causes the regression to go away, and a bunch of green benchmarks to pop up instead of red ones. This suggest that conservative measure isn't working very well and does not scale to these scenarios. It is also already taken care of by other conservative measures. I propose it is removed, to solve the regressions.
The entire ZGC perf suite was rerun (no red, only green), and tier1-3 was run. There isn't much potential for things to blow up as I just removed one parameter in the heuristic. So if anything nasty was to show up, it would be in the perf runs.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8271064: ZGC several jvm08 perf regressions after JDK-8268372

Reviewers

• Albert Mingkun Yang (@albertnetymk - Committer)
• Per Liden (@pliden - Reviewer)
• Thomas Schatzl (@tschatzl - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17 pull/298/head:pull/298
$ git checkout pull/298

Update a local copy of the PR:
$ git checkout pull/298
$ git pull https://git.openjdk.java.net/jdk17 pull/298/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 298

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17/pull/298.diff

[bridgekeeper]

👋 Welcome back eosterlund! 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]

@fisk 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.

[mlbridge]

Webrevs

• 00: Full (ab8fffe5)

[pliden]

Looks good!

[openjdk]

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

8271064: ZGC several jvm08 perf regressions after JDK-8268372

Reviewed-by: ayang, pliden, tschatzl

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 2 new commits pushed to the master branch:

• ada58d1: 8067223: [TESTBUG] Rename Whitebox API package
• f8fb571: 8271150: Remove EA from JDK 17 version string starting with Initial RC promotion on Aug 5, 2021(B34)

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

[fisk]

Thanks for the reviews, @albertnetymk, @pliden and @tschatzl

[fisk]

/integrate

[openjdk]

Going to push as commit 181483b.
Since your change was applied there have been 2 commits pushed to the master branch:

• ada58d1: 8067223: [TESTBUG] Rename Whitebox API package
• f8fb571: 8271150: Remove EA from JDK 17 version string starting with Initial RC promotion on Aug 5, 2021(B34)

Your commit was automatically rebased without conflicts.

[openjdk]

@fisk Pushed as commit 181483b.

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