-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8292265: Add old gen used field at G1HeapSummary JFR event #11303
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 sangheki! A progress list of the required criteria for merging this PR into |
/label add hotspot-gc, hotspot-jfr |
@sangheon The |
@sangheon |
Webrevs
|
size_t old_used_bytes = _monitoring_support->old_gen_used(); | ||
|
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.
On the one hand using the information from the MXBeans/MonitoringSupport and on the other hand recalculating this data manually, is likely to set us up for inconsistencies.
I recommend using MonitoringSupport
data for as many as possible values here.
From what I can see for young gc, this method is called as part of the G1JFRTracerMark
which encloses the G1MonitoringScope
, i.e. the data from MonitoringSupport
is all up to date. Same seems to be true for full gc.
So getting all data from MonitoringSupport
here is imo the best way to get consistent data vs. using parts of that data and recalculating others manually.
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.
Lgtm.
@sangheon 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 383 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 |
size_t survivor_used_bytes = _survivor.used_bytes(); | ||
size_t eden_used_bytes = _monitoring_support->eden_space_used(); | ||
size_t survivor_used_bytes = _monitoring_support->survivor_space_used(); | ||
size_t old_used_bytes = _monitoring_support->old_gen_used(); |
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 think it's best to include gen
in the name (across the whole PR), just to avoid the confusion of Old-region-type vs old-generation.
Thanks @tschatzl and @albertnetymk for your reviews. /integrate |
@sangheon This pull request has not yet been marked as ready for integration. |
/integrate |
Going to push as commit 8ea2a67.
Your commit was automatically rebased without conflicts. |
Hi all,
Can I have reviews for this change which adds 'old gen used' field at existing G1HeapSummary event?
Testing: tier1 ~ tier3
Thanks,
Sangheon
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11303/head:pull/11303
$ git checkout pull/11303
Update a local copy of the PR:
$ git checkout pull/11303
$ git pull https://git.openjdk.org/jdk pull/11303/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11303
View PR using the GUI difftool:
$ git pr show -t 11303
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11303.diff