-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
what window length would you recommend for calculating MA? |
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? |
You can use influxdb alongside to actually store the data in a time series format and the aggregate on the go. Just a suggestion. |
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? |
@stieglma Interesting. What version of Locust are you using? |
the one that got installed via pip: 0.8.1 |
Hi @stieglma ! Hopefully this is no longer an issue? Let me know if it is and we can reopen it. |
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.
The text was updated successfully, but these errors were encountered: