Median response times off
See original GitHub issue Name # reqs # fails Avg Min Max | Median req/s
----------------------------------------------------------------------------------------------------
POST long 1 0(0.00%) 6067 6067 6067 | 6100 0.00
POST short 1 0(0.00%) 1239 1239 1239 | 1200 0.20
----------------------------------------------------------------------------------------------------
Total 2 0(0.00%) 0.20
Name # reqs # fails Avg Min Max | Median req/s
--------------------------------------------------------------------------------------------------------------------------------------------
POST medium 7 0(0.00%) 468 199 1006 | 360
POST short 2 0(0.00%) 1063 574 1553 | 570 0.33
----------------------------------------------------------------------------------------------------
Total 9 0(0.00%) 1.00
This only seems to be an intermittent issue, but notice how the median response times are not within the bounds of min and max. Anyone else ran into a similar issue?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
See how quickly your team respond to, and close conversations
Median is the middle value in all of your response times. The middle value is what separates the higher half from the lower...
Read more >5 Ways to Reduce Customer Service Response Times
According to our own research of 1,000 companies, the average response time to respond to customer service requests is 12 hours and 10...
Read more >What Is The Average Police Response Time in the US?
When emergencies come up, it's comforting to know that first responders are typically only a few minutes away, regardless of where you are ......
Read more >Response Time Limits: Article by Jakob Nielsen
Response Times: The 3 Important Limits · 0.1 second · 1.0 second · 10 seconds ...
Read more >Email Response Times: How to Measure and Why It Matters
You may think 30 minutes is a decent time to aim for to make sure you don't miss any valuable opportunities, but a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In order to calculate the median response time, as well as response times for specific percentiles, without storing the response time for every single request, we keep a dict of the following format:
{response_time: numer_of_requests}
. In order to save memory we round the response time to only use two digits of precision (so that 6067 becomes 6100, 1239 -> 1200, 574 -> 570, and so on). Since that dict is used to calculate the median response times, while the exact response times are used when calculating min/max, it could happen that the median ends up outside of the min/max boundaries (especially for few requests).I guess it would probably be good to mention that we only use two digits precision for median & percentile response times, in the docs and the web UI.
#790 merged