-
Notifications
You must be signed in to change notification settings - Fork 3k
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
scale clients up and down during a run #1185
Comments
Could you share more about your scenario about scaling down, as it's kinda of symmetric with scaling up. If you only want to know how server's performance changes with different user load, I think scaling up should be enough. |
I must have missed that edit link, or has it been recently added? |
When #1168 is resolved you can just autoscale on k8s or some other autoscaling platform like an EC2 ASG. This solves the "tipped over the limits of the server" problem for slaves but of course you can't autoscale the master so the mast must always have enough resources for the duration of the test. |
Oh sorry, I misunderstood. |
also with step load pattern enabled, you can scale up the clients in small steps and it should be enough to identify the sweet spot. I think this feature can be closed for now. |
Is your feature request related to a problem?
During a run, I'd like to be able to increment or decrement the number of clients while consulting metrics from the system under test.
Describe the solution you'd like
Ideally, I'd like a box or menu item somewhere to let me set a new target number of workers and have locust scale to that.
Describe alternatives you've considered
#1001 would also be great, but I don't know what I want the steps to be before I start the master.
Currently I have to kill the master and workers and re-start them with new params whenever I want to change the number of workers.
The text was updated successfully, but these errors were encountered: