Concurrency thread group have different total samples in results with same configurations in jmeter
In jmeter, while using concurrency thread group,with same configurations I got different no. of total sanples in summary report. Can anyone explain why it happened?
I've below configurations:
Target Concurrency : 20
Ramp up time (sec) : 120
Ramp up Steps count : 10
Hold Target Rate time (sec) : 60
I've run the test twice, both time in summary report, i got 1704 samples and 1973 samples respectively.
concurrency jmeter
add a comment |
In jmeter, while using concurrency thread group,with same configurations I got different no. of total sanples in summary report. Can anyone explain why it happened?
I've below configurations:
Target Concurrency : 20
Ramp up time (sec) : 120
Ramp up Steps count : 10
Hold Target Rate time (sec) : 60
I've run the test twice, both time in summary report, i got 1704 samples and 1973 samples respectively.
concurrency jmeter
Concurrency Thread Group will maintain concurrency for Threads not samples. Sample count may differ based on response time, latency, etc
– Adnan
Nov 26 '18 at 5:36
add a comment |
In jmeter, while using concurrency thread group,with same configurations I got different no. of total sanples in summary report. Can anyone explain why it happened?
I've below configurations:
Target Concurrency : 20
Ramp up time (sec) : 120
Ramp up Steps count : 10
Hold Target Rate time (sec) : 60
I've run the test twice, both time in summary report, i got 1704 samples and 1973 samples respectively.
concurrency jmeter
In jmeter, while using concurrency thread group,with same configurations I got different no. of total sanples in summary report. Can anyone explain why it happened?
I've below configurations:
Target Concurrency : 20
Ramp up time (sec) : 120
Ramp up Steps count : 10
Hold Target Rate time (sec) : 60
I've run the test twice, both time in summary report, i got 1704 samples and 1973 samples respectively.
concurrency jmeter
concurrency jmeter
asked Nov 26 '18 at 5:30
DishDish
334
334
Concurrency Thread Group will maintain concurrency for Threads not samples. Sample count may differ based on response time, latency, etc
– Adnan
Nov 26 '18 at 5:36
add a comment |
Concurrency Thread Group will maintain concurrency for Threads not samples. Sample count may differ based on response time, latency, etc
– Adnan
Nov 26 '18 at 5:36
Concurrency Thread Group will maintain concurrency for Threads not samples. Sample count may differ based on response time, latency, etc
– Adnan
Nov 26 '18 at 5:36
Concurrency Thread Group will maintain concurrency for Threads not samples. Sample count may differ based on response time, latency, etc
– Adnan
Nov 26 '18 at 5:36
add a comment |
1 Answer
1
active
oldest
votes
JMeter waits for response from previous sampler prior to sending the next request so the deviation is due to response time
- Higher response time - less results
- Lower response time - more results
If you want to always have exact amount of sample results - use Throughput Controller in Total Executions
mode - this way JMeter will not run more samplers than you specify in the Throughput Controller.
Check out Running JMeter Samplers with Defined Percentage Probability article for more information on the Throughput Controller and ways of defining how often different requests will be executed and how to precisely control your workload.
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',
autoActivateHeartbeat: false,
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%2f53475204%2fconcurrency-thread-group-have-different-total-samples-in-results-with-same-confi%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
JMeter waits for response from previous sampler prior to sending the next request so the deviation is due to response time
- Higher response time - less results
- Lower response time - more results
If you want to always have exact amount of sample results - use Throughput Controller in Total Executions
mode - this way JMeter will not run more samplers than you specify in the Throughput Controller.
Check out Running JMeter Samplers with Defined Percentage Probability article for more information on the Throughput Controller and ways of defining how often different requests will be executed and how to precisely control your workload.
add a comment |
JMeter waits for response from previous sampler prior to sending the next request so the deviation is due to response time
- Higher response time - less results
- Lower response time - more results
If you want to always have exact amount of sample results - use Throughput Controller in Total Executions
mode - this way JMeter will not run more samplers than you specify in the Throughput Controller.
Check out Running JMeter Samplers with Defined Percentage Probability article for more information on the Throughput Controller and ways of defining how often different requests will be executed and how to precisely control your workload.
add a comment |
JMeter waits for response from previous sampler prior to sending the next request so the deviation is due to response time
- Higher response time - less results
- Lower response time - more results
If you want to always have exact amount of sample results - use Throughput Controller in Total Executions
mode - this way JMeter will not run more samplers than you specify in the Throughput Controller.
Check out Running JMeter Samplers with Defined Percentage Probability article for more information on the Throughput Controller and ways of defining how often different requests will be executed and how to precisely control your workload.
JMeter waits for response from previous sampler prior to sending the next request so the deviation is due to response time
- Higher response time - less results
- Lower response time - more results
If you want to always have exact amount of sample results - use Throughput Controller in Total Executions
mode - this way JMeter will not run more samplers than you specify in the Throughput Controller.
Check out Running JMeter Samplers with Defined Percentage Probability article for more information on the Throughput Controller and ways of defining how often different requests will be executed and how to precisely control your workload.
answered Nov 26 '18 at 9:29
Dmitri TDmitri T
74.3k33765
74.3k33765
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.
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%2f53475204%2fconcurrency-thread-group-have-different-total-samples-in-results-with-same-confi%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
Concurrency Thread Group will maintain concurrency for Threads not samples. Sample count may differ based on response time, latency, etc
– Adnan
Nov 26 '18 at 5:36