-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8246037: Shenandoah: update man pages to mention -XX:+UseShenandoahGC #26907
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
Conversation
|
👋 Welcome back rgithubli! A progress list of the required criteria for merging this PR into |
|
@rgithubli 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 140 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@earthling-amzn, @ysramakrishna, @JohnTortugo) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@rgithubli 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. |
Webrevs
|
|
/label remove graal |
|
@ysramakrishna |
|
/label add hotspot |
|
@rgithubli |
| `satb` | ||
| : Snapshot-at-the-beginning concurrent GC (three pass mark-evac-update). |
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.
This is a long-standing problem with the name. It kinda implies generational is not satb. It actually is. Maybe we should rename satb to single or something. A lot of bikeshedding would ensue.
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.
Renaming the value of an existing jvm arg sounds intrusive, unless we can add an alias link from satb to single? Alternatively, we probably can add comment in generational to indicate it's also satb?
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 agree. For non-experimental options, we can follow the established deprecate & rename protocol.
May be we could, in the inerim, add verbage in the description to avoid the confusion in the current naming as described by Aleksey.
src/java.base/share/man/java.md
Outdated
| the GC cycle. | ||
|
|
||
| `static` | ||
| : Trigger GC when free heap falls below the ShenandoahMinFreeThreshold. |
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.
Same here: ShenandoahMinFreeThreshold is experimental, it is not worth mentioning here. In fact, there are tunables for adaptive and compact as well, yet we do not (correctly!) mention them.
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.
True, other options respond to ShenandoahMinFreeThreshold as well. It's kinda hard to describe static option without mentioning the threshold.
- We could make the doc vague as in the shenandoah_globals.hpp:
trigger GC when free heap falls below the threshold. - I now wonder why
staticis a non experimental flag - it has to be used with other experimental flags. Maybe just drop static from man page as well?
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.
below a specified threshold might sound appropriately vague and render the flag unusable unless one consulted the code, underlining the experimental nature of it.
If the collector respects static as specified, it can be considered a good guardrail to use in anger. In fact, I know of teams that do in production. (For that matter, there are a couple who use compact as well.)
However, I am fine with eliding all experimental options, and in turn any non-experimental options that depend on experimental options (which however seems to be an anti-pattern to be avoided, if possible).
|
Updated for other comments except for renaming |
ysramakrishna
left a comment
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.
One small comment/suggestion. Rest looks good to me.
Approving modulo that suggestion.
|
|
|
@rgithubli This pull request has not yet been marked as ready for integration. |
ysramakrishna
left a comment
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.
Approved modulo a comment.
I also think we should to the extent possible make the listing of text common to man page and options list consistent. An example is the recent improvement you made in your most recent update to the man page for the heuristics option. There may be other changes to the man page that came about as a result of this review. It would make sense to make those changes, where applicable, also to shenandoah_globals. This latter need not hold up this ticket but can be addressed separately in a follow up.
src/java.base/share/man/java.md
Outdated
| Possible heuristics are the following (when `-XX:ShenandoahGCMode` is | ||
| `generational`, the only supported option is the default, `adaptive`): |
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.
Move the parenthetic part to the previous paragraph and out of parentheses.
|
Make sure that someone outside Shenandoah devs looks at this patch to sanity check how it reads. |
JohnTortugo
left a comment
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.
Ship it!
ysramakrishna
left a comment
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.
Re-reviewed. 🚢
(Apologies for all the bike-shedding!)
|
/integrate |
|
@rgithubli |
|
/sponsor |
|
Going to push as commit 5052a7e.
Your commit was automatically rebased without conflicts. |
|
@kdnilsen @rgithubli Pushed as commit 5052a7e. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Add documentation of Shenandoah to java man page
Aside from
-XX:+UseShenandoahGC, I picked flags from shenandoah_globals.hpp that are at product level but not experimental / diagnostic to avoid overwhelming info. Two additional flags match:ShenandoahGCModeandShenandoahGCHeuristicsProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26907/head:pull/26907$ git checkout pull/26907Update a local copy of the PR:
$ git checkout pull/26907$ git pull https://git.openjdk.org/jdk.git pull/26907/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26907View PR using the GUI difftool:
$ git pr show -t 26907Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26907.diff
Using Webrev
Link to Webrev Comment