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

Incorrect calculation of avg_response_time and current_rps in no_web mode #538

Closed
debugtalk opened this issue Feb 16, 2017 · 1 comment
Closed

Comments

@debugtalk
Copy link

debugtalk commented Feb 16, 2017

When I ran locust in no_web mode, I found out that the result will be calculated in every 2 seconds. However, each time when locust calculates avg_response_time and current_rps, it will use the whole history data of the current test.

avg_response_time = float(total_response_time) / num_requests

current_rps = avg(all_reqs)

I do not think this method does the right thing, shouldn't it calculate the instant average data only use the data in the interval 2 seconds?

@cgoldberg
Copy link
Member

please see current_rps implementation in stats.py:

def current_rps(self):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants