-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8351167: ZGC: Lazily initialize livemap #23907
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 jsikstro! A progress list of the required criteria for merging this PR into |
@jsikstro 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 98 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 |
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.
Looks good.
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.
Seems reasonable.
Thank you for the reviews! |
Going to push as commit 2672c40.
Your commit was automatically rebased without conflicts. |
Memory for the bitmap inside the livemap of a ZPage is currently allocated upon calling its constructor, which adds a latency overhead when allocating pages. As preparation for the Mapped Cache (JDK-8350441), but also as a standalone improvement, we want to instead lazily initialize the livemap's bitmap.
This patch holds off with allocating memory for the bitmap that the livemap uses until the livemap is written to the first time (i.e. by calling ZLiveMap::set). The effect of this is that the latency impact of allocating the bitmap will only be taken by GC threads and not by mutator threads, since only GC threads mark objects before pushing them onto the mark stack. This improvement will reduce page allocation latencies somewhat.
In addition to lazily allocating the bitmap, I've converted the static C-style cast to a checked cast for
ZPage::object_max_count()
, which is passed as the size to the bitmaps. This is because a value not contained in 32 bits will overflow with the C-style cast and give a too small bitmap when passed to the livemap. This is not an observed issue, just more of a sanity check.Testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23907/head:pull/23907
$ git checkout pull/23907
Update a local copy of the PR:
$ git checkout pull/23907
$ git pull https://git.openjdk.org/jdk.git pull/23907/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23907
View PR using the GUI difftool:
$ git pr show -t 23907
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23907.diff
Using Webrev
Link to Webrev Comment