-
Notifications
You must be signed in to change notification settings - Fork 29
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
Link information from JLM and MonitorContended events #56
Labels
Comments
yathamravali
added a commit
to yathamravali/openj9-utils
that referenced
this issue
May 21, 2021
Fixes: eclipse-openj9#56 Signed-Off-by: Ravali Yatham <[email protected]>
yathamravali
added a commit
to yathamravali/openj9-utils
that referenced
this issue
May 21, 2021
Fixes: eclipse-openj9#56 Signed-off-by: Ravali Yatham <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JLM (java lock monitor) gives us a summary of activity on monitors, whereas MonitorContended events are triggered for every monitor individually and they also can be used to compute the waiting time for a particular monitor operation (something that JLM does not do).
Ideally, we would first use the information from JLM to determine which monitors are expensive and then use the MonitorContended events to drill deeper and find stack traces for threads waiting on expensive monitors and for threads holding onto expensive monitors. To do that we need some common monitor information between the tho sources. There are two possibilities:
The text was updated successfully, but these errors were encountered: