Having a locust "die" or stop after one task

[arcoraven]

I'm trying to get an accurate number of how many users per second a particular endpoint I'm testing supports.

I'm not sure I like the min/max wait flags because it adds a bit of unknown into my data. For example, I don't know how long one task will take, so I can't accurately tell a user to "run this task precisely once per minute" (correct me if I'm wrong).

Is there a way I can tell a user to stop after running it's task once? That way, I can create 6k users spawning at 100 per sec. I'll know that I'm testing exactly 100 users per second for one minute.

P.S. This is similar to the "run through" each test once issue (#98), but that one references a deprecated command line flag.

[grahamrhay]

there is an (undocumented) StopLocust exception, which will stop that eventlet

[cedriclecoz]

Just what i was looking for :) thanks.

[ivoilic]

@grahamrhay Any more info on this? Is there a reason it isn't in the docs?

[grahamrhay]

no idea, sorry. I have nothing to do with the project, I just found it trawling the code (trying to solve a similar problem)

I would assume it isn't documented, because it isn't a feature. so the usual caveats of (ab)using implementation details

[sklrsn]

@grahamrhay Thanks.

[MaxAtkinson]

Update on this, I use the locust.exception.StopUser exception for this behaviour.