Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JFR Streaming: Do not take stacktraces for thread state events #384

Closed
thurka opened this issue Feb 2, 2022 · 1 comment
Closed

JFR Streaming: Do not take stacktraces for thread state events #384

thurka opened this issue Feb 2, 2022 · 1 comment
Assignees
@thurka
Labels
bug

Comments

@thurka
Copy link
Member

thurka commented Feb 2, 2022

JFR events jdk.ThreadSleep, jdk.ThreadPark, jdk.JavaMonitorEnter, jdk.JavaMonitorWait used for exact thread state monitoring currently come with stacktrace. Since the stacktrace is not needed for thread state monitoring, they can be omitted. This will lower the monitoring overhead and also lower the number of transferred bytes between VisualVM and monitored application.
@thurka thurka added the bug label Feb 2, 2022
@thurka thurka self-assigned this Feb 2, 2022
thurka added a commit that referenced this issue Feb 7, 2022
@thurka
GH-384 disabling of stacktraces fixed
fe8febd
@thurka
Copy link
Member Author

thurka commented Feb 7, 2022

Fixed in master.

@thurka thurka closed this as completed Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thurka thurka

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thurka