Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let hatch rate be provided by a callable #1353

Closed
steodorescu opened this issue Apr 23, 2020 · 4 comments
Closed

Let hatch rate be provided by a callable #1353

steodorescu opened this issue Apr 23, 2020 · 4 comments

Comments

@steodorescu
Copy link

I want to emulate loads that represent user activity based on a specific distribution.

Let' say the users have to login every morning. Some login around 8am, some login around 10am, most of them login around 9am.
It would be nice to tell locust to vary the client hatch rate following a statistical distribution of sorts over a given interval.

@heldic
Copy link

heldic commented Apr 28, 2020

I'd appreciate the same feature. In case you're not aware, you can opt to approximate a desired behaviour by shooting a bunch of POST requests to /swarm until predefined patterns/distributions are supported.

Regarding the desired feature: You might want to check out those two comments (and issues #1001 & #1002):

They suggest that such a feature might already be on the radar of @heyman, at least he's
also mentioned something related to this again in PR #1266:

Here are other changes that I think we should implement/consider for a 1.0. Most of them have been suggested/requested by others before at some point:
[...]

  • Re-work the step load feature. I'd like it to be something more general like a run plan with an API that one can hook into. It should also be able to both spawn and kill simulated users.

However, since there appears to be no open issue for this feature request anymore, so maybe this is a good even though PR #1281 already exists.

@cyberw
Copy link
Collaborator

cyberw commented Jun 6, 2020

Another way to work around it might be to do a sleep-loop until your specified time. Or use a cron job to start a completely new run of locust at a given time. I dont think we'll build this any time soon...

@cyberw
Copy link
Collaborator

cyberw commented Jul 13, 2020

(reopen with low prio, now that we use that label)

@cyberw cyberw reopened this Jul 13, 2020
@cyberw
Copy link
Collaborator

cyberw commented Sep 28, 2020

Superseeded by load shape feature

@cyberw cyberw closed this as completed Sep 28, 2020
@cyberw cyberw added the invalid label Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants