-
Notifications
You must be signed in to change notification settings - Fork 37
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
Usage tracking cleanup #260
Usage tracking cleanup #260
Conversation
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
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.
This looks like a good improvement. Thanks for sorting through these details. I assume we pass all the existing GenShen regression tests.
@earthling-amzn 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 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
There are no new regressions here. |
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 have left a few comments. Despite the improvements that you have made by some of the current refactoring, I am concerned about the organization of the allocation paths and believe that there are opportunities for cleaning these up, and specializing and slimming these allocation paths a bit more.
That can wait for later, but I'd like to take another pass at this once you have had a chance to read the review comments and in case those lead to any changes.
Thanks!
This is a good clean up, now that I see the big picture of the consolidation of the adjustments. I'll approve once you have had a chance to consider my review comments. |
Thanks for the review @ysramakrishna . I'll make changes based on your suggestions. |
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 for your patience with my review comments!
This looks good to me. 🚢
/integrate |
Going to push as commit d254fb2.
Your commit was automatically rebased without conflicts. |
@earthling-amzn Pushed as commit d254fb2. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
There are many nuances to tracing memory utilization. Shenandoah track's usage, waste by humongous objects, padding for promotion LABs alignment and all this is also tracked by generation, the heap and feeds into the heuristics and the pacer. The code to update all of these values and route them to the right places was spread across the allocation call stack. This change consolidates all of the logic into one method, invoked near the end of the allocation.
Progress
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/shenandoah.git pull/260/head:pull/260
$ git checkout pull/260
Update a local copy of the PR:
$ git checkout pull/260
$ git pull https://git.openjdk.org/shenandoah.git pull/260/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 260
View PR using the GUI difftool:
$ git pr show -t 260
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/shenandoah/pull/260.diff
Webrev
Link to Webrev Comment