-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8361726: Shenandoah: More detailed evacuation instrumentation #26222
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
base: master
Are you sure you want to change the base?
8361726: Shenandoah: More detailed evacuation instrumentation #26222
Conversation
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
@earthling-amzn The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
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.
Thanks. This instrumentation is helpful in evaluating further proposed changes.
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 few nits.
The extra detail is useful!
Shenandoah has
product only
instrumentation to track evacuation performance.
Did you mean to say non-product
instead of product only
above?
@earthling-amzn this pull request can not be integrated into git checkout categorize-evacuations
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
void begin_evacuation(Thread* thread, size_t bytes, ShenandoahAffiliation from, ShenandoahAffiliation to); | ||
|
||
// Multiple threads may attempt to evacuate the same object, but only the succeeding thread will end the evacuation. |
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.
Instead of only the succeeding thread will end the evacuation
, I might say: the unique thread that is successful will end the evacuation
. (Alternatively, replace "succeeding" with "successful"; the word "succeeding" as an adjective can be ambiguous in this context.)
GHA failure on macos looks unrelated (test was running G1). /integrate |
@earthling-amzn This pull request has not yet been marked as ready for integration. |
Shenandoah has
not product
instrumentation to track evacuation performance. This change introduces more detail by categorizing each evacuation as young, old or promotion.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26222/head:pull/26222
$ git checkout pull/26222
Update a local copy of the PR:
$ git checkout pull/26222
$ git pull https://git.openjdk.org/jdk.git pull/26222/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26222
View PR using the GUI difftool:
$ git pr show -t 26222
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26222.diff
Using Webrev
Link to Webrev Comment