Mixing
Result Mismatch between Jmeter and Webload in Performance testing
i'm new into performance testing. While doing performance testing of a website I found the results obtained by Jmeter were not matching with the results from Webload. So, i tested a simple website lifechanger.org through both the tools, with 1 Virtual user but still I got different different values.
Can anyone has any help on this.
Please read below values obtained through both the tools.
URL: Lifechanger.org
Only Throughput matched in this scenario. Any help will be grateful.
Thanks in advance.
performance jmeter performance-testing load-testing webloadui
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
add a comment |
i'm new into performance testing. While doing performance testing of a website I found the results obtained by Jmeter were not matching with the results from Webload. So, i tested a simple website lifechanger.org through both the tools, with 1 Virtual user but still I got different different values.
Can anyone has any help on this.
Please read below values obtained through both the tools.
URL: Lifechanger.org
Only Throughput matched in this scenario. Any help will be grateful.
Thanks in advance.
performance jmeter performance-testing load-testing webloadui
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
add a comment |
i'm new into performance testing. While doing performance testing of a website I found the results obtained by Jmeter were not matching with the results from Webload. So, i tested a simple website lifechanger.org through both the tools, with 1 Virtual user but still I got different different values.
Can anyone has any help on this.
Please read below values obtained through both the tools.
URL: Lifechanger.org
Only Throughput matched in this scenario. Any help will be grateful.
Thanks in advance.
performance jmeter performance-testing load-testing webloadui
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
i'm new into performance testing. While doing performance testing of a website I found the results obtained by Jmeter were not matching with the results from Webload. So, i tested a simple website lifechanger.org through both the tools, with 1 Virtual user but still I got different different values.
Can anyone has any help on this.
Please read below values obtained through both the tools.
URL: Lifechanger.org
Only Throughput matched in this scenario. Any help will be grateful.
Thanks in advance.
performance jmeter performance-testing load-testing webloadui
performance jmeter performance-testing load-testing webloadui
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
edited Nov 22 '18 at 9:52
Sandeep Singh
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
asked Nov 22 '18 at 9:28
Sandeep SinghSandeep Singh
442
442
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You should not be comparing 2 load testing tools against each other, you should be comparing them to the real browser and configure both to match real browser's behavior, otherwise your test will not make a lot of sense.
Things to consider:
- You need to make sure that you set the load testing tool to retrieve all embedded resources from the page (images, scripts, styles, fonts, etc.)
- You need to make sure it's being done in parallel (as this is what real browsers do)
- You need to make sure it's being done only once (or according to Cache-Control headers), in other words implement browser's cache.
- You need to accept/send back HTTP Cookies
- You need to send appropriate HTTP Headers like User-Agent or Accept-Encoding
- You need to properly simulate AJAX calls, like embedded resources they're being executed in parallel
Ideally well-behaved load testing tool should give you the same timings as browser developer tools on its Network tab.
More information:
- How to make JMeter behave more like a real browser
- WebLoad Scripting Guide
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
domcontentloadedis for page DOM (i.e. HTML code), andLoadis for everything else (scripts, rendering, etc.)
– Dmitri T
Nov 22 '18 at 14:41
add a comment |
As throughput and hits/sec were matching and we were having different response time and latencies on Jmeter and webload, I did some research on the time difference on Latencies and response time. Please find below observations.
Latency in Jmeter : JMeter measures the latency from just before sending the request to just after the first response has been received. Thus the time includes all the processing needed to assemble the request as well as assembling the first part of the response, which in general will be longer than one byte. Protocol analyzers (such as Wireshark) measure the time when bytes are actually sent/received over the interface. The JMeter time should be closer to that which is experienced by a browser or other application client.
Latency in Webload: The time that elapsed since a request was sent until the Virtual Client received the first byte of data.
As Jmeter is working from perspective of application client where it’s also considering the time taken on post processing of DOM, that may be the reason we are having increased time shown up in Jmeter which is in seconds. This is the way Jmeter works on the other hand Webload is showing time without processing of data, the time it takes to receive data in DOM, which is always in millisec.
References:
1). https://jmeter.apache.org/usermanual/glossary.html
2). Webload Help Section in the app
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
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%2f53427671%2fresult-mismatch-between-jmeter-and-webload-in-performance-testing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should not be comparing 2 load testing tools against each other, you should be comparing them to the real browser and configure both to match real browser's behavior, otherwise your test will not make a lot of sense.
Things to consider:
- You need to make sure that you set the load testing tool to retrieve all embedded resources from the page (images, scripts, styles, fonts, etc.)
- You need to make sure it's being done in parallel (as this is what real browsers do)
- You need to make sure it's being done only once (or according to Cache-Control headers), in other words implement browser's cache.
- You need to accept/send back HTTP Cookies
- You need to send appropriate HTTP Headers like User-Agent or Accept-Encoding
- You need to properly simulate AJAX calls, like embedded resources they're being executed in parallel
Ideally well-behaved load testing tool should give you the same timings as browser developer tools on its Network tab.
More information:
- How to make JMeter behave more like a real browser
- WebLoad Scripting Guide
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
domcontentloadedis for page DOM (i.e. HTML code), andLoadis for everything else (scripts, rendering, etc.)
– Dmitri T
Nov 22 '18 at 14:41
add a comment |
You should not be comparing 2 load testing tools against each other, you should be comparing them to the real browser and configure both to match real browser's behavior, otherwise your test will not make a lot of sense.
Things to consider:
- You need to make sure that you set the load testing tool to retrieve all embedded resources from the page (images, scripts, styles, fonts, etc.)
- You need to make sure it's being done in parallel (as this is what real browsers do)
- You need to make sure it's being done only once (or according to Cache-Control headers), in other words implement browser's cache.
- You need to accept/send back HTTP Cookies
- You need to send appropriate HTTP Headers like User-Agent or Accept-Encoding
- You need to properly simulate AJAX calls, like embedded resources they're being executed in parallel
Ideally well-behaved load testing tool should give you the same timings as browser developer tools on its Network tab.
More information:
- How to make JMeter behave more like a real browser
- WebLoad Scripting Guide
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
domcontentloadedis for page DOM (i.e. HTML code), andLoadis for everything else (scripts, rendering, etc.)
– Dmitri T
Nov 22 '18 at 14:41
add a comment |
You should not be comparing 2 load testing tools against each other, you should be comparing them to the real browser and configure both to match real browser's behavior, otherwise your test will not make a lot of sense.
Things to consider:
- You need to make sure that you set the load testing tool to retrieve all embedded resources from the page (images, scripts, styles, fonts, etc.)
- You need to make sure it's being done in parallel (as this is what real browsers do)
- You need to make sure it's being done only once (or according to Cache-Control headers), in other words implement browser's cache.
- You need to accept/send back HTTP Cookies
- You need to send appropriate HTTP Headers like User-Agent or Accept-Encoding
- You need to properly simulate AJAX calls, like embedded resources they're being executed in parallel
Ideally well-behaved load testing tool should give you the same timings as browser developer tools on its Network tab.
More information:
- How to make JMeter behave more like a real browser
- WebLoad Scripting Guide
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
You should not be comparing 2 load testing tools against each other, you should be comparing them to the real browser and configure both to match real browser's behavior, otherwise your test will not make a lot of sense.
Things to consider:
- You need to make sure that you set the load testing tool to retrieve all embedded resources from the page (images, scripts, styles, fonts, etc.)
- You need to make sure it's being done in parallel (as this is what real browsers do)
- You need to make sure it's being done only once (or according to Cache-Control headers), in other words implement browser's cache.
- You need to accept/send back HTTP Cookies
- You need to send appropriate HTTP Headers like User-Agent or Accept-Encoding
- You need to properly simulate AJAX calls, like embedded resources they're being executed in parallel
Ideally well-behaved load testing tool should give you the same timings as browser developer tools on its Network tab.
More information:
- How to make JMeter behave more like a real browser
- WebLoad Scripting Guide
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
answered Nov 22 '18 at 9:55
Dmitri TDmitri T
72.8k33663
72.8k33663
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
domcontentloadedis for page DOM (i.e. HTML code), andLoadis for everything else (scripts, rendering, etc.)
– Dmitri T
Nov 22 '18 at 14:41
add a comment |
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
domcontentloadedis for page DOM (i.e. HTML code), andLoadis for everything else (scripts, rendering, etc.)
– Dmitri T
Nov 22 '18 at 14:41
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
Hi Dmitri, firstly thanks. I would like you to please help a bit more. If i go to Network tab in dev tools, i founded domcontentload and load time as , Domcontentloaded- 3.95 s & 2.88 s, Load - 5.91 s & 3.8s for my 2 pages respectively. From this Can i say, Load time is average of about 5 sec? And, what Domcontentload means here? If you have any document link for measuring performance from dev tools please do share with me.
– Sandeep Singh
Nov 22 '18 at 14:09
domcontentloaded is for page DOM (i.e. HTML code), and Load is for everything else (scripts, rendering, etc.)– Dmitri T
Nov 22 '18 at 14:41
domcontentloaded is for page DOM (i.e. HTML code), and Load is for everything else (scripts, rendering, etc.)– Dmitri T
Nov 22 '18 at 14:41
add a comment |
As throughput and hits/sec were matching and we were having different response time and latencies on Jmeter and webload, I did some research on the time difference on Latencies and response time. Please find below observations.
Latency in Jmeter : JMeter measures the latency from just before sending the request to just after the first response has been received. Thus the time includes all the processing needed to assemble the request as well as assembling the first part of the response, which in general will be longer than one byte. Protocol analyzers (such as Wireshark) measure the time when bytes are actually sent/received over the interface. The JMeter time should be closer to that which is experienced by a browser or other application client.
Latency in Webload: The time that elapsed since a request was sent until the Virtual Client received the first byte of data.
As Jmeter is working from perspective of application client where it’s also considering the time taken on post processing of DOM, that may be the reason we are having increased time shown up in Jmeter which is in seconds. This is the way Jmeter works on the other hand Webload is showing time without processing of data, the time it takes to receive data in DOM, which is always in millisec.
References:
1). https://jmeter.apache.org/usermanual/glossary.html
2). Webload Help Section in the app
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
add a comment |
As throughput and hits/sec were matching and we were having different response time and latencies on Jmeter and webload, I did some research on the time difference on Latencies and response time. Please find below observations.
Latency in Jmeter : JMeter measures the latency from just before sending the request to just after the first response has been received. Thus the time includes all the processing needed to assemble the request as well as assembling the first part of the response, which in general will be longer than one byte. Protocol analyzers (such as Wireshark) measure the time when bytes are actually sent/received over the interface. The JMeter time should be closer to that which is experienced by a browser or other application client.
Latency in Webload: The time that elapsed since a request was sent until the Virtual Client received the first byte of data.
As Jmeter is working from perspective of application client where it’s also considering the time taken on post processing of DOM, that may be the reason we are having increased time shown up in Jmeter which is in seconds. This is the way Jmeter works on the other hand Webload is showing time without processing of data, the time it takes to receive data in DOM, which is always in millisec.
References:
1). https://jmeter.apache.org/usermanual/glossary.html
2). Webload Help Section in the app
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
add a comment |
As throughput and hits/sec were matching and we were having different response time and latencies on Jmeter and webload, I did some research on the time difference on Latencies and response time. Please find below observations.
Latency in Jmeter : JMeter measures the latency from just before sending the request to just after the first response has been received. Thus the time includes all the processing needed to assemble the request as well as assembling the first part of the response, which in general will be longer than one byte. Protocol analyzers (such as Wireshark) measure the time when bytes are actually sent/received over the interface. The JMeter time should be closer to that which is experienced by a browser or other application client.
Latency in Webload: The time that elapsed since a request was sent until the Virtual Client received the first byte of data.
As Jmeter is working from perspective of application client where it’s also considering the time taken on post processing of DOM, that may be the reason we are having increased time shown up in Jmeter which is in seconds. This is the way Jmeter works on the other hand Webload is showing time without processing of data, the time it takes to receive data in DOM, which is always in millisec.
References:
1). https://jmeter.apache.org/usermanual/glossary.html
2). Webload Help Section in the app
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
As throughput and hits/sec were matching and we were having different response time and latencies on Jmeter and webload, I did some research on the time difference on Latencies and response time. Please find below observations.
Latency in Jmeter : JMeter measures the latency from just before sending the request to just after the first response has been received. Thus the time includes all the processing needed to assemble the request as well as assembling the first part of the response, which in general will be longer than one byte. Protocol analyzers (such as Wireshark) measure the time when bytes are actually sent/received over the interface. The JMeter time should be closer to that which is experienced by a browser or other application client.
Latency in Webload: The time that elapsed since a request was sent until the Virtual Client received the first byte of data.
As Jmeter is working from perspective of application client where it’s also considering the time taken on post processing of DOM, that may be the reason we are having increased time shown up in Jmeter which is in seconds. This is the way Jmeter works on the other hand Webload is showing time without processing of data, the time it takes to receive data in DOM, which is always in millisec.
References:
1). https://jmeter.apache.org/usermanual/glossary.html
2). Webload Help Section in the app
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
answered Nov 23 '18 at 11:17
Sandeep SinghSandeep Singh
442
442
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%2f53427671%2fresult-mismatch-between-jmeter-and-webload-in-performance-testing%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
