Comments (3)
The intention of the current API isn't that one must specify a range, but rather just a default. To define your own waiting function one would just override the wait function and skip declaring min_wait and max_wait:
class User(Locust):
def wait(self):
""" my custom wait function """
self._sleep(x)
However, I like the wait_time better (as long as the wait function is still there, in case one would like to hook into it), since the user won't need to know about either the sleep function or gevent.sleep().
I also think I like the random_between and constant proposal, but I would prefer the arguments to be specified in milliseconds.
from locust.
Sure, be aware of the workings of gevent.sleep() feels something only power users should need to worry about.
Regarding milliseconds vs seconds: I see no use of going against the common practice in Python of using the unit of seconds. time.time() and time.sleep() both operate using seconds.
from locust.
I think that when specifying two integers, the chance that someone wrongly assumes that it will chose an integer between the two, will increase. I can certainly see myself doing it.
I would prefer milliseconds but it's no deal breaker, since they both work of course :).
from locust.
Related Issues (20)
- Wrong distribution of virtual users by user classes HOT 5
- Running two services test with different volume to be run in parallel HOT 3
- Abnormal Response Time Percentiles Reported After a Load Increase HOT 3
- Custom Threshold Rules HOT 3
- Event spawning_complete fires every time a user is created HOT 5
- S HOT 1
- Remove legacy UI HOT 1
- When there is an error in the FAILURES of the front-end page when there is a worker, there is no escape. HOT 7
- Can you consider json objects to automatically generate pressure test scripts HOT 2
- Add date to charts in web UI HOT 2
- Update FastHttpUser to use geventhttpclients UserAgent instead of our own HOT 1
- Why defining run_time on worker node raises an error HOT 2
- Pin the headers and aggregated row to the top and bottom of the window HOT 1
- Locust insists on using IPv6 despite being in an IPv4 stack. HOT 4
- Possibly performance regression in the latest versions of locust HOT 9
- The time of the downloaded html report is not correct HOT 3
- Custom client (GCP pubsub) resulting in segfault for 2+ users HOT 3
- Running Sequential task set tasks with continuous generated data HOT 1
- User Classes with Empty Tasks Results in TypeError: 'NoneType' object is not iterable HOT 2
- how the requests # being counted in my test case ? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from locust.