Make wait_time default to zero (vote up/down for this ticket please :)
See original GitHub issueToday all Locust classes need to have a wait_time specified. I suggest we change that to make no wait time the default. I think having no wait time is what a reasonable user would expect, and it significantly lowers the bar for new locust users.
Please vote up or down (or add any arguments you may have).
This would change the simplest possible locust file from:
from locust import Locust
from locust.wait_time import constant
class MyLocust(Locust):
wait_time = constant(0)
...
To:
from locust import Locust
class MyLocust(Locust):
...
Issue Analytics
- State:
- Created 3 years ago
- Reactions:17
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Arizona 2022 General Election Publicity Pamphlet
1 With 11 ballot measures and nearly 500 arguments submitted by the public, the guide is one of the largest ever produced for...
Read more >DOS Voting & Election Information
The official Pennsylvania election and voter information website is vote.pa.gov. Learn More ...
Read more >1006786 - Harassment and signal squelchening Description
They had no right what so ever to "steal my computer overnight" I understand that they did this to millions of people, so...
Read more >About native Support time duration metrics
Full resolution time; Requester wait time; Agent wait time; On-hold time. Tip: In the graphics below, green indicates time counted and gray ...
Read more >Election Security Rumor vs. Reality
When a ballot cannot be read by a scanner at a voting site, election officials apply procedures to securely store the ballots until...
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
Thanks for your input!
In my mind a locust instance represents a single concurrent user. If I have a test case where I want to simulate ~100 concurrent users (maybe selected from a database/csv of 100.000 users) I would use 100 locusts, not 100.000. This very much represents “real users”, but having a sleep after each iteration is not “more real” (because the time between one user leaving and another user arriving is not typically something that is a key feature of the load/realism)
Having zero wait time is the standard in pretty much every other load test tool I have seen and I believe 99.9% of users would expect a zero sleep time between iterations if there isn’t one specified so I think readability does not suffer at all.
I dont expect to convince anyone but these are my main arguments 😃
Sorry, but I’ll have to vote down for this, for a couple of reasons:
Just my 2 cents.