What exactly are the count and duration values in JFR Thread Contention
up vote
0
down vote
favorite
I have an multi-threaded application that runs for 1m9s (with 56 concurrent threads). The JFR screenshot of the contentions is show below. What is not clear to me are:
- What does the Count field indicate? The number of times the Lock has been acquired?
- What does the Average value indicate? And how is it that the Duration (= count * average) greater than the total execution time of the application?
Thanks,
java jfr
asked Nov 22 at 3:07
Sami Hailu
15116
add a comment |
up vote
0
down vote
favorite
I have an multi-threaded application that runs for 1m9s (with 56 concurrent threads). The JFR screenshot of the contentions is show below. What is not clear to me are:
- What does the Count field indicate? The number of times the Lock has been acquired?
- What does the Average value indicate? And how is it that the Duration (= count * average) greater than the total execution time of the application?
Thanks,
java jfr
asked Nov 22 at 3:07
Sami Hailu
15116
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an multi-threaded application that runs for 1m9s (with 56 concurrent threads). The JFR screenshot of the contentions is show below. What is not clear to me are:
- What does the Count field indicate? The number of times the Lock has been acquired?
- What does the Average value indicate? And how is it that the Duration (= count * average) greater than the total execution time of the application?
Thanks,
java jfr
asked Nov 22 at 3:07
Sami Hailu
15116
I have an multi-threaded application that runs for 1m9s (with 56 concurrent threads). The JFR screenshot of the contentions is show below. What is not clear to me are:
- What does the Count field indicate? The number of times the Lock has been acquired?
- What does the Average value indicate? And how is it that the Duration (= count * average) greater than the total execution time of the application?
Thanks,
java jfr
java jfr
asked Nov 22 at 3:07
Sami Hailu
15116
asked Nov 22 at 3:07
Sami Hailu
15116
asked Nov 22 at 3:07
Sami Hailu
15116
asked Nov 22 at 3:07
Sami Hailu
15116
asked Nov 22 at 3:07
Sami Hailu
15116
15116
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
If I remember correctly the tab you're looking at there shows the number of times a thread has been blocked waiting on each lock grouped by the class (i.e. it counts multiple instances of the lock as the same here). The reason you might see a cumulative duration longer than the total runtime of the application is that it counts the wait time of each thread. Since you have 56 threads running (assuming that they run for the entire runtime of the application) the maximum amount of time that can be spent blocking on one particular lock is around 64 minutes (69s*56).
answered Nov 22 at 10:24
Henrik Dafgård
515
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53423304%2fwhat-exactly-are-the-count-and-duration-values-in-jfr-thread-contention%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
If I remember correctly the tab you're looking at there shows the number of times a thread has been blocked waiting on each lock grouped by the class (i.e. it counts multiple instances of the lock as the same here). The reason you might see a cumulative duration longer than the total runtime of the application is that it counts the wait time of each thread. Since you have 56 threads running (assuming that they run for the entire runtime of the application) the maximum amount of time that can be spent blocking on one particular lock is around 64 minutes (69s*56).
answered Nov 22 at 10:24
Henrik Dafgård
515
add a comment |
up vote
2
down vote
If I remember correctly the tab you're looking at there shows the number of times a thread has been blocked waiting on each lock grouped by the class (i.e. it counts multiple instances of the lock as the same here). The reason you might see a cumulative duration longer than the total runtime of the application is that it counts the wait time of each thread. Since you have 56 threads running (assuming that they run for the entire runtime of the application) the maximum amount of time that can be spent blocking on one particular lock is around 64 minutes (69s*56).
answered Nov 22 at 10:24
Henrik Dafgård
515
add a comment |
up vote
2
down vote
up vote
2
down vote
If I remember correctly the tab you're looking at there shows the number of times a thread has been blocked waiting on each lock grouped by the class (i.e. it counts multiple instances of the lock as the same here). The reason you might see a cumulative duration longer than the total runtime of the application is that it counts the wait time of each thread. Since you have 56 threads running (assuming that they run for the entire runtime of the application) the maximum amount of time that can be spent blocking on one particular lock is around 64 minutes (69s*56).
answered Nov 22 at 10:24
Henrik Dafgård
515
If I remember correctly the tab you're looking at there shows the number of times a thread has been blocked waiting on each lock grouped by the class (i.e. it counts multiple instances of the lock as the same here). The reason you might see a cumulative duration longer than the total runtime of the application is that it counts the wait time of each thread. Since you have 56 threads running (assuming that they run for the entire runtime of the application) the maximum amount of time that can be spent blocking on one particular lock is around 64 minutes (69s*56).
answered Nov 22 at 10:24
Henrik Dafgård
515
answered Nov 22 at 10:24
Henrik Dafgård
515
answered Nov 22 at 10:24
Henrik Dafgård
515
answered Nov 22 at 10:24
Henrik Dafgård
515
515
add a comment |
add a comment |
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%2f53423304%2fwhat-exactly-are-the-count-and-duration-values-in-jfr-thread-contention%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
