-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8239508 JFR: @RemoveFields #16411
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
8239508 JFR: @RemoveFields #16411
Conversation
|
👋 Welcome back egahlin! A progress list of the required criteria for merging this PR into |
mgronlun
left a comment
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.
Nice!
|
@egahlin 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 23 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 |
|
/integrate |
|
Going to push as commit 2d5829a.
Your commit was automatically rebased without conflicts. |
This enhancement introduces an annotation that controls the presence of implicit fields for an event.
For native events, the metadata.xml file controls the existence of the fields "eventThread" "duration” and "stackTrace”. For Java events, there is nothing similar. This outage has been known since the inception of the jdk.jfr API. At that time, we decided to ignore it and write 0 for “eventThread”, “stackTrace”, and ”duration”. The gain was a simplified programming model with one annotation, i.e. StackTrace, instead of two, i.e. StackTrace and HasStackTrace, to determine if a value should be recorded.
With the removal of event handlers (JDK-8282420 ) and use of the new Class-File API (JDK-8318124) this capability can be added to Java events at a lower implementation cost. Also, we are considering adding other fields, such as allocation, cpuTime, or socketRead/Write, that can occur between a call to Event::begin() and Event::end().
There is still uncertainty about the design of the annotation, so it is currently only accessible to JDK events. Instead of a separate annotation per field, i.e. HasStackTrace, HasEventThread, and HasDuration, there is one annotation, RemoveFields, that provides a list of fields that should be dropped. This allows for a corresponding annotation, AddFields, to be included in the future, for example, to add the field cpuTime.
The benefits of the change are:
Testing: test/jdk/jdk/jfr/ tier1 + tier2
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16411/head:pull/16411$ git checkout pull/16411Update a local copy of the PR:
$ git checkout pull/16411$ git pull https://git.openjdk.org/jdk.git pull/16411/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16411View PR using the GUI difftool:
$ git pr show -t 16411Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16411.diff
Webrev
Link to Webrev Comment