https://bz.apache.org/bugzilla/show_bug.cgi?id=63198
Bug ID: 63198
Summary: Throughput\Response Time Vs Request and Latency Vs
Request graphs global request/s don't line up
Product: JMeter
Version: 5.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: regression
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.2
Created attachment 36451
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36451&action=edit
Load script
While trying to write up a simple validation test for JMeter for internal
process reasons. A coworker noticed that the Response Time Vs Request and
Latency Vs Request data didn't make any sense with JMeter 5.0/5.1 but looks
perfectly ok with 4.0.
As you can see the attached test is very simple and I manage to record ~1461
total requests.
However, the dashboard output generated via:
...\jmeter.bat -n -t <path>\TestBing_com.jmx -l <path>\TestLogfile.data -e
-o <path>\JMeterReport
In 5.0 and 5.1 the total transaction per second graphed values never exceed 18.
However, the Response Time Vs Request has data points at:
1000 global req/s, 2000 global req/s, 3000 global req/s, 4000 global req/s.
Even the dashboard's total transactions/s doesn't exceed ~27.5.
The Latency Vs Request graph has similar data points.
The data in these graphs for 4.0 had more reasonable 2.0 and 7.0 global req/s
data points.
This seems like a bug, but is it me misunderstanding a change in 5.0 to JMeter?
Thanks...
--
You are receiving this mail because:
You are the assignee for the bug.
