-
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
Samples with response_time None crashes stats.py #1087
Comments
I agree that it makes sense to be able to report requests without response times so that they wouldn't taint the stats for ordinary requests. The #1088 PR should have tests. I'm a little bit concerned that the changes could have unintended effects since the code up until now have always assumed that each request has a response time. That might be an unfounded concern though, but in any case, I think these changes should come with multiple tests where non-response-time requests are made both by themselves, as well as together with "normal" requests that have a response time. |
I'll try to add add tests for None response times mixed with integer response times |
Cool! Hopefully that should be able to catch any unintended consequences if there are any (I've been looking a bit more at the code, and couldn't see any immediate problems with the changes). |
When I added the tests I immediately found some issues :) (related to average and median calculation) I am trying to fix them... |
I've fixed the issues with calculating averages and median. |
Certain async protocols/clients (like websockets, MQ etc) dont really have a response time. They should be able to report a None response time. Using zero is not good enough, because a test may contain a mix of synchronous requests (like HTTP) and async, and we dont want to "taint" the average response time with zeroes.
Result:
The text was updated successfully, but these errors were encountered: