Bug 65191 - JMeter not calculating accurate response time.
Summary: JMeter not calculating accurate response time.
Status: NEEDINFO
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.4.1
Hardware: PC All
: P2 critical (vote)
Target Milestone: JMETER_5.5
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-17 12:37 UTC by Max
Modified: 2021-06-06 14:48 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Max 2021-03-17 12:37:44 UTC
I have a http sampler. When I run with "Downlaod embedded resources" with 6 parallel connection. it generates total 8 connections but the response time will be addition of response times of first two resources. Rest resources have very less around 50 ms of response times. So I can easily see that response time of the main sampler is addition of the first two resources being downloaded which have response times of around 1 sec.
Comment 1 Felix Schumacher 2021-06-06 14:48:37 UTC
Can you give a simple jtl file with results, that show this problem?

Beware, that the parent sampler will show the duration of all requests as experienced by the "user". If requests are done in parallel, the longest duration will be "counted".

I have done a little experiment with a test page, that contains only links to "images":

$ cat webapps/ROOT/test.html 
<img src="image.jsp?one" />
<img src="image.jsp?two" />
<img src="image.jsp?three" />
<img src="image.jsp?four" />
<img src="image.jsp?five" />
<img src="image.jsp?six" />
<img src="image.jsp?seven" />
<img src="image.jsp?eight" />
---

$ cat webapps/ROOT/image.jsp 
<%
   Thread.sleep(300);
%>

OK
---

When I call test.html it will take around 600 ms, which makes sense, as with 6 concurrent requests we will have two "images" that will have to wait for 300 ms to get a free worker.