apache / apache/jmeter

Report / Dashboard : If granularity is below 1 sec, the Throughput graphs will be incorrect

Open
#4,118 3 comments 0 reactions 0 assignees View on GitHub
enhancement os: All P2
Dominant language
Java
Stars
9.5k
Forks
2.3k
Avg merge
1d 22h
Merged PRs (30d)
5

Description

**Tamas Szabadi** ([Bug 60149](https://bz.apache.org/bugzilla//show_bug.cgi?id=60149&redirect=false)):
When the granularity is set below 1 second, the TPS and the other throughput graphs will be incorrect. For example if the granularity is 500ms, the TPS will be doubled on the graph.

Steps to reproduce:
1. Set jmeter.reportgenerator.overall_granularity = 500
2. Run some tests (the attached example runs a TCP Sampler based custom sampler for the EPP protocol) with Reporting dashboard generated.

Here you can see in the jmeter log (attached) the average TPS:

...
2016/09/19 05:24:00 INFO - jmeter.reporters.Summariser: summary + 33000 in 00:00:26 = 1246.7/s Avg: 53 Min: 30 Max: 118 Err: 0 (0.00%) Active: 70 Started: 70 Finished: 0
2016/09/19 05:24:00 INFO - jmeter.reporters.Summariser: summary = 33003 in 00:00:37 = 890.0/s Avg: 53 Min: 30 Max: 118 Err: 0 (0.00%)
2016/09/19 05:24:30 INFO - jmeter.reporters.Summariser: summary + 37300 in 00:00:30 = 1244.5/s Avg: 55 Min: 30 Max: 200 Err: 0 (0.00%) Active: 70 Started: 70 Finished: 0
2016/09/19 05:24:30 INFO - jmeter.reporters.Summariser: summary = 70303 in 00:01:07 = 1048.5/s Avg: 54 Min: 30 Max: 200 Err: 0 (0.00%)
2016/09/19 05:25:00 INFO - jmeter.reporters.Summariser: summary + 37200 in 00:00:30 = 1237.2/s Avg: 55 Min: 30 Max: 165 Err: 0 (0.00%) Active: 70 Started: 70 Finished: 0
2016/09/19 05:25:00 INFO - jmeter.reporters.Summariser: summary = 107503 in 00:01:37 = 1106.9/s Avg: 54 Min: 30 Max: 200 Err: 0 (0.00%)
...

3. Wait for the tests to finish and check the Transaction Per Second graph in the generated Reporting Dashboard

Expected results:
The same result should be in the dashboard report, around 1200 TPS.

Actual results:
The actual result in the graph seems to be doubled, around 2400 TPS.

Additional information:

- The full generated dashboard or the test result was above the 1MB limit, but I can send if it would be helpful. Right now I attached the jmeter.log and the TPS graph image.
- If I set the granularity to above or equal to 1 second, the graph will be correct, so this is what I am doing currently.

Created attachment [bug.zip](https://apache.github.io/jmeter-bugzilla-attachments/49/60149/34274/bug.zip): jmeter log, TPS graph generated by the reporting dashboard

Votes in Bugzilla: 2
OS: All

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.