-
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
could we report 99.9% percentile in CSV file? #1040
Comments
IMHO 99% and 100% should be enough. |
+1 for adding p99.9 and p99.99 I've done some load tests and statistically, 99, 99.9, and 99.99 are all different. Also its meaning depends on each use case (i.e. SLA), but it should be in reports. |
100% for this. If you are load testing a service that has human users these percentiles become very important. It's complicated why but there's a good explanation in this video |
I misunderstood this, I thought you were talking about the "real time" csv output (which is per-two-second statistics, where p99.9 would not even make theoretical sense, except for extremely high throughput). But I guess we're talking about the stats you get from /stats/distribution/csv ? I definitely see the use of p99.9 and p99.99 there, let me see if I can add them easily... Personally I use external reporting (timescale+grafana) for everything (see https://github.com/SvenskaSpel/locust-plugins if you are interested). |
Fixed! |
Description of issue
could we report percentile with better granularity, like 99.9? considering that tail latency is more and more critical these days.
The text was updated successfully, but these errors were encountered: