-
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
Ability to specify percentiles you need for response time chart #2311
Comments
Sounds reasonably useful. I’d prefer |
Note that for csv reports you can already overwrite locust.stats.PERCENTILES_TO_REPORT https://docs.locust.io/en/stable/configuration.html#customization-of-statistics-settings |
Thank you for the reply. I'll take this style "--percentiles 0.8,0.99" and will send PR. |
👍 Or maybe this too fits better as an attribute on the stats module, now that I think about it… the choicr between what is command line settings and code values is kind of arbitrary, but since stats config is already in code.. |
Is your feature request related to a problem? Please describe.
The software I'm currently testing by locust requires 98% < 1.0 sec and 99.5 % < 2.0 sec response time performance. The performance requirement will vary based on software or project etc.. It would be better that percentiles on performance char is configurable not only median and 95% percentile.
Benefit of having this function on chart page is, we can see necessary percentile info in response time chart dynamically every minutes.
Describe the solution you'd like
Ideal solution would be to add new command line argument like attachment. If the parameters are not specified, default value median and 95% are used
locust -f locust.py --percentile1 0.8 --percentile2 0.99
then displays like this
Performance chart
report page
Describe alternatives you've considered
applying to stats page is alternatives, but it's overall percentiles not time series
Additional context
I have updated locust for the ability on my local repo folked from orignal.
The text was updated successfully, but these errors were encountered: