-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8328792: Parallel: Refactor PSParallelCompact::summary_phase #18451
Conversation
👋 Welcome back ayang! A progress list of the required criteria for merging this PR into |
@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:
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 54 new commits pushed to the
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 |
@albertnetymk The following label will be automatically applied to this pull request:
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. |
cf3db3b
to
2f3bb06
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
2f3bb06
to
69d7d54
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
69d7d54
to
3903dc4
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
3903dc4
to
39d57fe
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
39d57fe
to
f2c5da6
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
f2c5da6
to
285c198
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
285c198
to
4c6bc83
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
4c6bc83
to
8c76efb
Compare
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
old_space_total_live += pointer_delta(_space_info[id].new_top(), | ||
_space_info[id].space()->bottom()); | ||
if (maximum_compaction || is_old_gen_overflowing || is_interval_ended || is_region_full) { | ||
_maximum_compaction_gc_num = total_invocations; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the function name, we don't expect it to do more than reassess_maximum_compaction
, additionally this modification also requires that we call reassess_maximum_compaction
even when maximum_compaction
is already true. Is is possible to decouple these two: reassess_maximum_compaction
and _maximum_compaction_gc_num = total_invocations
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_maximum_compaction_gc_num
is on the same abstraction level as the checking denoted as "JVM flags". Separating them will probably make code harder to follow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I agree, but it is a minor issue, not a blocker.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also somewhat agree that changing _maximum_compaction_gc_num
seems unexpected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok.
old_space_total_live += pointer_delta(_space_info[id].new_top(), | ||
_space_info[id].space()->bottom()); | ||
if (maximum_compaction || is_old_gen_overflowing || is_interval_ended || is_region_full) { | ||
_maximum_compaction_gc_num = total_invocations; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also somewhat agree that changing _maximum_compaction_gc_num
seems unexpected.
We can revisit around Thanks for review. /integrate |
Going to push as commit 273df62.
Your commit was automatically rebased without conflicts. |
@albertnetymk Pushed as commit 273df62. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The diff is not easy to follow; it's better to read the new code directly.
summary_phase
contains the gist of collecting live-size from each space, calculating dense-prefix and summarizing old-space using dense-prefix.(There is slight improvement to the "Summary Phase", but it takes only ~0.01ms for either case.)
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18451/head:pull/18451
$ git checkout pull/18451
Update a local copy of the PR:
$ git checkout pull/18451
$ git pull https://git.openjdk.org/jdk.git pull/18451/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18451
View PR using the GUI difftool:
$ git pr show -t 18451
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18451.diff
Webrev
Link to Webrev Comment