How to simulate a load test of 500tps using JMeter
I am using JMeter for testing my REST API. The API must handle around 100 tps load. I am using following hardware for generating load:
CPU - 8 Cores
RAM - 16 Gb
3.0 GHz Intel Xeon Platinum Processor
_JAVA_OPTIONS = -Xms1g -Xmx12g
Now I have single http GET request.
My JMeter configuration:
number of users - 10000
ramp up time - 100 seconds
The above configuration means 100 concurrent users per second, and that one request is equal to 1 trasaction per second.
Am I interpreting it correctly?
Also, how should I plan to test my API for 500tps load?
My server runs out of memory if I increase the number of threads.
jmeter
edited Dec 28 '18 at 19:04
S Jade
166118
asked Dec 28 '18 at 17:13
user978601user978601
111
add a comment |
I am using JMeter for testing my REST API. The API must handle around 100 tps load. I am using following hardware for generating load:
CPU - 8 Cores
RAM - 16 Gb
3.0 GHz Intel Xeon Platinum Processor
_JAVA_OPTIONS = -Xms1g -Xmx12g
Now I have single http GET request.
My JMeter configuration:
number of users - 10000
ramp up time - 100 seconds
The above configuration means 100 concurrent users per second, and that one request is equal to 1 trasaction per second.
Am I interpreting it correctly?
Also, how should I plan to test my API for 500tps load?
My server runs out of memory if I increase the number of threads.
jmeter
edited Dec 28 '18 at 19:04
S Jade
166118
asked Dec 28 '18 at 17:13
user978601user978601
111
add a comment |
I am using JMeter for testing my REST API. The API must handle around 100 tps load. I am using following hardware for generating load:
CPU - 8 Cores
RAM - 16 Gb
3.0 GHz Intel Xeon Platinum Processor
_JAVA_OPTIONS = -Xms1g -Xmx12g
Now I have single http GET request.
My JMeter configuration:
number of users - 10000
ramp up time - 100 seconds
The above configuration means 100 concurrent users per second, and that one request is equal to 1 trasaction per second.
Am I interpreting it correctly?
Also, how should I plan to test my API for 500tps load?
My server runs out of memory if I increase the number of threads.
jmeter
edited Dec 28 '18 at 19:04
S Jade
166118
asked Dec 28 '18 at 17:13
user978601user978601
111
I am using JMeter for testing my REST API. The API must handle around 100 tps load. I am using following hardware for generating load:
CPU - 8 Cores
RAM - 16 Gb
3.0 GHz Intel Xeon Platinum Processor
_JAVA_OPTIONS = -Xms1g -Xmx12g
Now I have single http GET request.
My JMeter configuration:
number of users - 10000
ramp up time - 100 seconds
The above configuration means 100 concurrent users per second, and that one request is equal to 1 trasaction per second.
Am I interpreting it correctly?
Also, how should I plan to test my API for 500tps load?
My server runs out of memory if I increase the number of threads.
jmeter
jmeter
edited Dec 28 '18 at 19:04
S Jade
166118
asked Dec 28 '18 at 17:13
user978601user978601
111
edited Dec 28 '18 at 19:04
S Jade
166118
asked Dec 28 '18 at 17:13
user978601user978601
111
edited Dec 28 '18 at 19:04
S Jade
166118
edited Dec 28 '18 at 19:04
S Jade
166118
edited Dec 28 '18 at 19:04
S Jade
166118
166118
asked Dec 28 '18 at 17:13
user978601user978601
111
asked Dec 28 '18 at 17:13
user978601user978601
111
asked Dec 28 '18 at 17:13
user978601user978601
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The above configuration doesn't mean 100 concurrent users per second. It also does not mean one request is equal to 1 trasaction per second whatever you mean by this.
The above configuration means that
- JMeter will start 100 users each second
- The users will start execute the request as fast as they can
- Once virtual user finishes the request it will be shut down
The actual number of concurrent users and transactions per seconds depends on your server response time, i.e. if response time will be 1 second - you will have 100 transactions per second, if response time will be 2 seconds - you will have 50 transactions per second, if response time will be 0.5 seconds - you will have 200 transactions per second.
If your goal is to achieve 100 or 500 tps - I would recommend using Throughput Shaping Timer and Concurrency Thread Group combination. They can be put together using feedback function so JMeter will automatically start new threads in order to reach/maintain the defined concurrency.
Both test elements can be installed using JMeter Plugins Manager
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1388504%2fhow-to-simulate-a-load-test-of-500tps-using-jmeter%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
The above configuration doesn't mean 100 concurrent users per second. It also does not mean one request is equal to 1 trasaction per second whatever you mean by this.
The above configuration means that
- JMeter will start 100 users each second
- The users will start execute the request as fast as they can
- Once virtual user finishes the request it will be shut down
The actual number of concurrent users and transactions per seconds depends on your server response time, i.e. if response time will be 1 second - you will have 100 transactions per second, if response time will be 2 seconds - you will have 50 transactions per second, if response time will be 0.5 seconds - you will have 200 transactions per second.
If your goal is to achieve 100 or 500 tps - I would recommend using Throughput Shaping Timer and Concurrency Thread Group combination. They can be put together using feedback function so JMeter will automatically start new threads in order to reach/maintain the defined concurrency.
Both test elements can be installed using JMeter Plugins Manager
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
add a comment |
The above configuration doesn't mean 100 concurrent users per second. It also does not mean one request is equal to 1 trasaction per second whatever you mean by this.
The above configuration means that
- JMeter will start 100 users each second
- The users will start execute the request as fast as they can
- Once virtual user finishes the request it will be shut down
The actual number of concurrent users and transactions per seconds depends on your server response time, i.e. if response time will be 1 second - you will have 100 transactions per second, if response time will be 2 seconds - you will have 50 transactions per second, if response time will be 0.5 seconds - you will have 200 transactions per second.
If your goal is to achieve 100 or 500 tps - I would recommend using Throughput Shaping Timer and Concurrency Thread Group combination. They can be put together using feedback function so JMeter will automatically start new threads in order to reach/maintain the defined concurrency.
Both test elements can be installed using JMeter Plugins Manager
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
add a comment |
The above configuration doesn't mean 100 concurrent users per second. It also does not mean one request is equal to 1 trasaction per second whatever you mean by this.
The above configuration means that
- JMeter will start 100 users each second
- The users will start execute the request as fast as they can
- Once virtual user finishes the request it will be shut down
The actual number of concurrent users and transactions per seconds depends on your server response time, i.e. if response time will be 1 second - you will have 100 transactions per second, if response time will be 2 seconds - you will have 50 transactions per second, if response time will be 0.5 seconds - you will have 200 transactions per second.
If your goal is to achieve 100 or 500 tps - I would recommend using Throughput Shaping Timer and Concurrency Thread Group combination. They can be put together using feedback function so JMeter will automatically start new threads in order to reach/maintain the defined concurrency.
Both test elements can be installed using JMeter Plugins Manager
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
The above configuration doesn't mean 100 concurrent users per second. It also does not mean one request is equal to 1 trasaction per second whatever you mean by this.
The above configuration means that
- JMeter will start 100 users each second
- The users will start execute the request as fast as they can
- Once virtual user finishes the request it will be shut down
The actual number of concurrent users and transactions per seconds depends on your server response time, i.e. if response time will be 1 second - you will have 100 transactions per second, if response time will be 2 seconds - you will have 50 transactions per second, if response time will be 0.5 seconds - you will have 200 transactions per second.
If your goal is to achieve 100 or 500 tps - I would recommend using Throughput Shaping Timer and Concurrency Thread Group combination. They can be put together using feedback function so JMeter will automatically start new threads in order to reach/maintain the defined concurrency.
Both test elements can be installed using JMeter Plugins Manager
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
answered Dec 28 '18 at 17:30
Dmitri TDmitri T
22112
22112
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1388504%2fhow-to-simulate-a-load-test-of-500tps-using-jmeter%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
