Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response time graph seems to be an average of all data #667

Closed
lyonzy opened this issue Oct 23, 2017 · 8 comments
Closed

Response time graph seems to be an average of all data #667

lyonzy opened this issue Oct 23, 2017 · 8 comments
Labels

Comments

@lyonzy
Copy link

lyonzy commented Oct 23, 2017

Description of issue / feature request

In the web UI, the response time graph seems to show response time for the entire test run, which I feel is unsuitable for a graph format. At a given x-point on the graph, the current graph shows the average of all data up until then, whereas it would be more useful to see the average of data at that time.

Expected behavior

Response time might be better displayed as a moving average rather than a complete average.

Actual behavior

Response time is calculated as an absolute/complete average rather than moving average, which means spikes are significantly 'dampened'. This also doesn't seem to fit a graph format - an absolute average would be suitable for a single number (e.g. the Statistics tab) and a moving average would be better suited for a time-based view like a line graph.

@cgoldberg
Copy link
Member

might be better displayed as a moving average

what window length would you recommend for calculating MA?
(could be configurable)

@lyonzy
Copy link
Author

lyonzy commented Nov 28, 2017

Yeah configurable would be nice. For a default though, what about the same as the RPS? i.e. average of the results that came in at the time, so basically instantaneous. Are you able to confirm the current behaviour?

@appunnicer13
Copy link

You can use influxdb alongside to actually store the data in a time series format and the aggregate on the go. Just a suggestion.

@heyman
Copy link
Member

heyman commented Mar 2, 2018

The response time is calculated using a moving window of the (approximately) last 10 seconds. If it's not, it's a bug. Could you provide more info on why you think it's showing the total average?

@heyman heyman added bug and removed feature request labels Mar 2, 2018
@stieglma
Copy link

Not sure if it is the total average, but it is definitely not a moving average of the last 10 seconds for me. Attached you find a picture which shows this quite good. Somewhere around 06:00 there was a spike to >170 seconds, after resetting the stats it went back down to ~26 seconds. (the part from 9:00 onwards can be ignored, I stopped/started measurements there)
movingaveragebug

@heyman
Copy link
Member

heyman commented Mar 23, 2018

@stieglma Interesting. What version of Locust are you using?

@stieglma
Copy link

the one that got installed via pip: 0.8.1

@cyberw
Copy link
Collaborator

cyberw commented Oct 20, 2019

Hi @stieglma ! Hopefully this is no longer an issue? Let me know if it is and we can reopen it.

@cyberw cyberw closed this as completed Oct 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants