-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8338389: [JFR] Long strings should be added to the string pool #20596
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
8338389: [JFR] Long strings should be added to the string pool #20596
Conversation
|
👋 Welcome back jnordstrom! A progress list of the required criteria for merging this PR into |
|
@jaokim 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 89 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@mgronlun) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Webrevs
|
|
I've fixed the nits for the test, thanks @turbanoff and @mgronlun! This now needs a re-review. Thanks! |
|
Thank you @mgronlun! /integrate |
|
/sponsor |
|
Going to push as commit d5c6158.
Your commit was automatically rebased without conflicts. |
When committing JFR events with string data longer than 128 characters, the string isn't added to the JFR string pool. In scenarios with many events containing large string values, this can lead to very large JFR recordings. This is mostly the case for custom events containing f.i. SQL strings or other data. In the case where the string data consist of mostly duplicate data, adding them to the string pool has been shown to reduce the recording size by a factor of 10.
This change will add all longer strings (>128 characters) to the string pool. Strings of length 16-128 are still added using the same pre-cache methodology as before. The raised StringPool.MAX_LIMIT is used by
jdk.jfr.internal.event.EventWriter::putStringto determine which strings to add to the pool.Testing
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/20596/head:pull/20596$ git checkout pull/20596Update a local copy of the PR:
$ git checkout pull/20596$ git pull https://git.openjdk.org/jdk.git pull/20596/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 20596View PR using the GUI difftool:
$ git pr show -t 20596Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/20596.diff
Webrev
Link to Webrev Comment