question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make wait_time default to zero (vote up/down for this ticket please :)

See original GitHub issue

Today 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:closed
  • Created 3 years ago
  • Reactions:17
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

6reactions
cyberwcommented, Apr 6, 2020

Thanks for your input!

  1. 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)

  2. 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 😃

3reactions
anuj-ssharmacommented, Apr 6, 2020

Sorry, but I’ll have to vote down for this, for a couple of reasons:

  1. A locust class represents a real user and a real user would not ever have a 0 second wait time. By setting the default to 0 seconds we are moving a locust away from representing a real user.
  2. If in a case the wait time is 0 seconds, then asking it to be written explicity would improve readability.

Just my 2 cents.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found