Skip to content
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

8346194: Improve G1 pre-barrier C2 cost estimate #23862

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tschatzl
Copy link
Contributor

@tschatzl tschatzl commented Mar 3, 2025

Hi all,

please review this change that modifies pre-barrier node costs for loop-unrolling to only consider the fast path. The reasoning is similar to zgc (and the new costs as well): only the part of the barrier inlined into the main code stream, as the slow path is laid out separately and does/should not directly affect performance (particularly if there is no marking going on).

There are no differences/impact in performance since the post barrier cost is still very large, which fill be fixed elsewhere.

Testing: gha, perf testing standalone (neither micros nor actual benchmarks give any difference outside of variance), testing with JDK-8342382

Hth,
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-8346194: Improve G1 pre-barrier C2 cost estimate (Enhancement - P4)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23862

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

Using diff file

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

Using Webrev

Link to Webrev Comment

Hi all,

  please review this change that modifies pre-barrier node costs for
loop-unrolling to only consider the fast path. The reasoning is similar
to zgc (and the new costs as well): only the part of the barrier inlined
into the main code stream, as the slow path is laid out separately and
does/should not directly affect performance (particularly if there is no
marking going on).

There are no differences/impact in performance since the post barrier cost
is still very large, which fill be fixed elsewhere.

Testing: gha, perf testing standalone (neither micros nor actual
benchmarks give any difference outside of variance), testing with JDK-8342382

Hth,
  Thomas
@bridgekeeper
Copy link

bridgekeeper bot commented Mar 3, 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 Mar 3, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk bot changed the title 8346194 8346194: Improve G1 pre-barrier C2 cost estimate Mar 3, 2025
@openjdk
Copy link

openjdk bot commented Mar 3, 2025

@tschatzl 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 the hotspot hotspot-dev@openjdk.org label Mar 3, 2025
@tschatzl tschatzl marked this pull request as ready for review March 3, 2025 12:32
@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 3, 2025
@mlbridge
Copy link

mlbridge bot commented Mar 3, 2025

Webrevs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot hotspot-dev@openjdk.org rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

1 participant