Rally task detailed 95%ile Response Times different from HTML graphics report
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rally |
Fix Released
|
High
|
Alexander Maretskiy |
Bug Description
Viewing a task's response timings with rally task detailed or upon task completion shows a different 95%ile response timing than after plotting HTML graphics with rally task report.
Example:
# rally task detailed ac5f0429-
...
+------
| Response Times (sec) |
+------
| action | min | median | 90%ile | 95%ile | max | avg | success | count |
+------
| total | 0.166 | 0.517 | 1.544 | 1.938 | 3.616 | 0.715 | 100.0% | 5000 |
+------
...
vs
# rally task report ac5f0429-
...
"table": {"rows": [["total", 0.
.544, 1.941, 3.616, 0.715, "100.0%", 5000.0]], "cols": ["Action", "Min (sec)", "Median (sec)", "90%ile (sec)", "95%ile (sec)", "Max (sec)", "Avg (sec)", "Success", "Count"]},
...
In the above example, rally task detailed shows a 95%ile response timing of 1.938 and rally task report ends up showing a 95%ile response timing of 1.941.
Changed in rally: | |
importance: | Low → High |
Changed in rally: | |
assignee: | nobody → Alexander Maretskiy (maretskiy) |
This is a kind of known issues and the root cause of that is the fact that cli and html report use different approaches of calculating statistics.
Cli command processes the whole data at once (old manner) but html report generation uses streaming processing (it gives benefits in case of huge amount of data). However small difference is possible in percentile values, which is not critical in most cases.