Inference of Locust result
Clash Royale CLAN TAG#URR8PPP
Inference of Locust result
Locust Report
NUM REQUESTS 500
NUM CLIENTS 50
NUM HATCH RATE 10
Name # reqs # fails Avg Min Max | Median req/s
--------------------------------------------------------------------------------------------------------------------------------------------
POST /someurl 549 0(0.00%) 43 27 103 | 44 40.90
--------------------------------------------------------------------------------------------------------------------------------------------
Total 549 0(0.00%) 40.90
Percentage of the requests completed within given times
Name # reqs 50% 66% 75% 80% 90% 95% 98% 99% 100%
--------------------------------------------------------------------------------------------------------------------------------------------
POST /someurl 549 44 48 50 51 55 57 63 68 103
--------------------------------------------------------------------------------------------------------------------------------------------
Here, the number of failure cases are 0.
The number of requests is 500 but, total requests in report is 549
Can anyone please explain why there is inconsistency.
Thanks in advance!
--no-reset-stats
yeah I'm running with
--no-reset-stats
. But still, I'm afraid that I couldnt understand.– Keerthana Prabhakaran
Aug 13 at 9:13
--no-reset-stats
1 Answer
1
When you start clients, Locust does two things:
--no-reset-stats
Because you are using --no-reset-stats
this means that any of the requests made in the hatching period will count towards your total, even though the count for 500 does not start until all are hatched.
--no-reset-stats
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Are you running it with
--no-reset-stats
? If so, that will... not reset stats once the clients hatch completely (which is when the 500 requests start).– Elysian Fields
Aug 12 at 17:43