-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8372412: Increase buffer size for ring-buffer events in CollectedHeap #28476
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 7 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 |
|
Going to push as commit 81ea144.
Your commit was automatically rebased without conflicts. |
Hello,
The buffer size we changed to when separating GC and Metaspace printing code is too small for Parallel and Serial (and maybe also for long-running programs in general). I suggest we bump the buffer-size to 1024 bytes. This also leaves room for more lengthy prints, which ZGC might have if running on a machine with many NUMA nodes.
The default number of events stored in each ring-buffer is 20, controlled via the diagnostic flag
LogEventsBufferEntries. In it's default setting, the total memory usage of each ring-buffer (Metaspace and Heap) will increase from (512 bytes * 20) 10KB to (1024 * 20) 20KB.For completeness, the content of the ring-buffers are only printed in hs_err files, using the
-XX:+PrintVMInfoAtExit(diagnostic flag) or usingjcmd VM.infoTesting:
java -XX:+UseParalellGC/UseSerialGC -XX:+PrintVMInfoAtExit ...to see that the message is not cut-off any longer.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28476/head:pull/28476$ git checkout pull/28476Update a local copy of the PR:
$ git checkout pull/28476$ git pull https://git.openjdk.org/jdk.git pull/28476/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28476View PR using the GUI difftool:
$ git pr show -t 28476Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28476.diff
Using Webrev
Link to Webrev Comment