[Bug 65191] New: JMeter not calculating accurate response time.

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=65191

            Bug ID: 65191
           Summary: JMeter not calculating accurate response time.
           Product: JMeter
           Version: 5.4.1
          Hardware: PC
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: piyush.dm@gmail.com
  Target Milestone: JMETER_5.5

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 65191] JMeter not calculating accurate response time.

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=65191

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #2 from Felix Schumacher <fe...@internetallee.de> ---
Closing, as no further information has been given.

Feel free to re-open this ticket, if you can provide further information.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 65191] JMeter not calculating accurate response time.

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=65191

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All
             Status|NEW                         |NEEDINFO

--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.