How to use pprof mutex/block profiling?
up vote
0
down vote
favorite
When trying to detect concurrency bottleneck, I use /debug/pprof/mutex and /debug/pprof/block and output the data to svg.
Both charts show in a similar way, DAG with time on the edges, but they show quite a different call graph. For example, I use a connection Pool, functions related to that connection are totally gone from block profiling, but they are the main time contribution in mutex profiling.
Here is my understanding:
The time on the edge in mutex profiling is the time goroutines hold mutexes.
The time on the edge in block profiling is the time goroutines get blocked.
So if I want to optimize my program to have better concurrency, I should check the path showing in "block profiling", right?
go pprof asked Nov 22 at 4:05
Ray Wu
414523
add a comment |
up vote
0
down vote
favorite
When trying to detect concurrency bottleneck, I use /debug/pprof/mutex and /debug/pprof/block and output the data to svg.
Both charts show in a similar way, DAG with time on the edges, but they show quite a different call graph. For example, I use a connection Pool, functions related to that connection are totally gone from block profiling, but they are the main time contribution in mutex profiling.
Here is my understanding:
The time on the edge in mutex profiling is the time goroutines hold mutexes.
The time on the edge in block profiling is the time goroutines get blocked.
So if I want to optimize my program to have better concurrency, I should check the path showing in "block profiling", right?
go pprof asked Nov 22 at 4:05
Ray Wu
414523
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When trying to detect concurrency bottleneck, I use /debug/pprof/mutex and /debug/pprof/block and output the data to svg.
Both charts show in a similar way, DAG with time on the edges, but they show quite a different call graph. For example, I use a connection Pool, functions related to that connection are totally gone from block profiling, but they are the main time contribution in mutex profiling.
Here is my understanding:
The time on the edge in mutex profiling is the time goroutines hold mutexes.
The time on the edge in block profiling is the time goroutines get blocked.
So if I want to optimize my program to have better concurrency, I should check the path showing in "block profiling", right?
go pprof asked Nov 22 at 4:05
Ray Wu
414523
When trying to detect concurrency bottleneck, I use /debug/pprof/mutex and /debug/pprof/block and output the data to svg.
Both charts show in a similar way, DAG with time on the edges, but they show quite a different call graph. For example, I use a connection Pool, functions related to that connection are totally gone from block profiling, but they are the main time contribution in mutex profiling.
Here is my understanding:
The time on the edge in mutex profiling is the time goroutines hold mutexes.
The time on the edge in block profiling is the time goroutines get blocked.
So if I want to optimize my program to have better concurrency, I should check the path showing in "block profiling", right?
go pprof go pprof asked Nov 22 at 4:05
Ray Wu
414523
asked Nov 22 at 4:05
Ray Wu
414523
asked Nov 22 at 4:05
Ray Wu
414523
asked Nov 22 at 4:05
Ray Wu
414523
asked Nov 22 at 4:05
Ray Wu
414523
414523
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423735%2fhow-to-use-pprof-mutex-block-profiling%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
