-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
perfschema: support query cpu/memory/mutex/block/allocs/goroutines flamegraph by SQL (#12986) #13009
Conversation
…amegraph by SQL (#12986) Signed-off-by: Lonng <heng@lonng.org>
Signed-off-by: Lonng <heng@lonng.org>
Signed-off-by: Lonng <heng@lonng.org>
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.
LGTM
Any conflicted files? |
@djshow832 |
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.
LGTM
Sorry @djshow832, you don't have permission to trigger auto merge event on this branch. |
Your auto merge job has been accepted, waiting for 12950 |
/run-all-tests |
Signed-off-by: Lonng heng@lonng.org
Cherry-pick #12986 for release-3.0
What problem does this PR solve?
Currently, we need to get the profile file through the HTTP interface, and then convert the profile file into a flame map through an external tool. This process is very inefficient and cumbersome.
What is changed and how it works?
Use SQL to directly obtain flamegraph to help us improve diagnostic efficiency.
Note: This PR is part of Hackathon 2019 TBSSQL2.0.
eg:
And we can filter some leavies easily.
Check List
Tests
Code changes
Related changes
Release note