Jmeter: Scenario to test 5 users with ramp up 1 hour to trigger 10 thousand requests
Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.
- Thread group - users - 5; ramp up - 3600 (secs); loop count - 1
- Loop controller value: 10000
- Request is under this Loop Controller
When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.
Are these configurations correct to achieve our scenario load testing output.
Please suggest and guide.
jmeter
asked Nov 13 at 5:24
la1
9819
add a comment |
Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.
- Thread group - users - 5; ramp up - 3600 (secs); loop count - 1
- Loop controller value: 10000
- Request is under this Loop Controller
When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.
Are these configurations correct to achieve our scenario load testing output.
Please suggest and guide.
jmeter
asked Nov 13 at 5:24
la1
9819
add a comment |
Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.
- Thread group - users - 5; ramp up - 3600 (secs); loop count - 1
- Loop controller value: 10000
- Request is under this Loop Controller
When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.
Are these configurations correct to achieve our scenario load testing output.
Please suggest and guide.
jmeter
asked Nov 13 at 5:24
la1
9819
Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.
- Thread group - users - 5; ramp up - 3600 (secs); loop count - 1
- Loop controller value: 10000
- Request is under this Loop Controller
When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.
Are these configurations correct to achieve our scenario load testing output.
Please suggest and guide.
jmeter
jmeter
asked Nov 13 at 5:24
la1
9819
asked Nov 13 at 5:24
la1
9819
asked Nov 13 at 5:24
la1
9819
asked Nov 13 at 5:24
la1
9819
asked Nov 13 at 5:24
la1
9819
9819
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your configuration is a little bit incorrect. In your setup
- JMeter will start with one user which will execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- etc.
You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"
Instead I would suggest the following configuration:
Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)
Request
Constant Throughput Timer with Target Throughput:
166.6666666667
Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)
In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.
You can install custom thread groups using JMeter Plugins Manager
answered Nov 13 at 6:25
Dmitri T
68.7k33458
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
1
It should be sufficient to changeCalculate Throughput Based Ontothis thread only
– Dmitri T
Nov 13 at 6:52
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
1
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
1
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
|
show 1 more 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%2f53274333%2fjmeter-scenario-to-test-5-users-with-ramp-up-1-hour-to-trigger-10-thousand-requ%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
Your configuration is a little bit incorrect. In your setup
- JMeter will start with one user which will execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- etc.
You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"
Instead I would suggest the following configuration:
Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)
Request
Constant Throughput Timer with Target Throughput:
166.6666666667
Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)
In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.
You can install custom thread groups using JMeter Plugins Manager
answered Nov 13 at 6:25
Dmitri T
68.7k33458
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
1
It should be sufficient to changeCalculate Throughput Based Ontothis thread only
– Dmitri T
Nov 13 at 6:52
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
1
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
1
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
|
show 1 more comment
Your configuration is a little bit incorrect. In your setup
- JMeter will start with one user which will execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- etc.
You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"
Instead I would suggest the following configuration:
Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)
Request
Constant Throughput Timer with Target Throughput:
166.6666666667
Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)
In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.
You can install custom thread groups using JMeter Plugins Manager
answered Nov 13 at 6:25
Dmitri T
68.7k33458
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
1
It should be sufficient to changeCalculate Throughput Based Ontothis thread only
– Dmitri T
Nov 13 at 6:52
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
1
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
1
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
|
show 1 more comment
Your configuration is a little bit incorrect. In your setup
- JMeter will start with one user which will execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- etc.
You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"
Instead I would suggest the following configuration:
Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)
Request
Constant Throughput Timer with Target Throughput:
166.6666666667
Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)
In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.
You can install custom thread groups using JMeter Plugins Manager
answered Nov 13 at 6:25
Dmitri T
68.7k33458
Your configuration is a little bit incorrect. In your setup
- JMeter will start with one user which will execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- In 12 minutes another user will start and execute 10 000 requests as fast as it can
- etc.
You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"
Instead I would suggest the following configuration:
Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)
Request
Constant Throughput Timer with Target Throughput:
166.6666666667
Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)
In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.
You can install custom thread groups using JMeter Plugins Manager
answered Nov 13 at 6:25
Dmitri T
68.7k33458
answered Nov 13 at 6:25
Dmitri T
68.7k33458
answered Nov 13 at 6:25
Dmitri T
68.7k33458
answered Nov 13 at 6:25
Dmitri T
68.7k33458
68.7k33458
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
1
It should be sufficient to changeCalculate Throughput Based Ontothis thread only
– Dmitri T
Nov 13 at 6:52
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
1
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
1
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
|
show 1 more comment
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
1
It should be sufficient to changeCalculate Throughput Based Ontothis thread only
– Dmitri T
Nov 13 at 6:52
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
1
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
1
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
– la1
Nov 13 at 6:39
1
1
It should be sufficient to change
Calculate Throughput Based On to this thread only– Dmitri T
Nov 13 at 6:52
It should be sufficient to change
Calculate Throughput Based On to this thread only– Dmitri T
Nov 13 at 6:52
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
– la1
Nov 14 at 5:29
1
1
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
– Dmitri T
Nov 14 at 5:34
1
1
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
– Dmitri T
Nov 14 at 5:35
|
show 1 more 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%2f53274333%2fjmeter-scenario-to-test-5-users-with-ramp-up-1-hour-to-trigger-10-thousand-requ%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
