-
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
number locusts must be a multiple of the number of slaves #112
Comments
Ah, I see. The reason for the current behaviour is just simplicity/laziness (easier to just order each slave to spawn the same number of locust users) and I think I was reasoning that when you have a really high number of slave machines, you're likely to also have them run many more magnitudes of locust users so it shouldn't matter. However, it shouldn't be very hard to modify the code in MasterLocustRunner.start_hatching ( Line 262 in 01ecb04
|
Fixed in the commit referenced above. I just distributed the remaining locusts by adding one locust for each slave until theres no more locusts left to distribute. |
Just got around to having a look at this afternoon. Thanks for the speedy fix! |
Great! I found a small bug when testing this out. If one tried to spawn fewer locusts than the number of connected slaves, we would still spawn one user per slave. I've fixed this is fb2bd53. It's a one line fix and ~20 lines test, plus two other tests I wrote while debugging it :). |
Excellent! |
yeah, I spotted that too but figured I'd have a go at fixing it rather than complaining about a (somewhat) nitpicky thing. Thanks for beating me to it ;) |
Actually this still looks a little broken in current master. I've seen that at least the number of locusts can overrun what you ask for. I'll do a bit more digging today if I can dig out the root cause or at least narrow it down a bit. |
Is this issue still persisting? I have 16 Slaves in my setup and have 30 different types of users defined. Seems like the minimum load I can run is with 16 * 30 = 480 locusts. |
This is definitely still an issue for me, but it doesn't seem as clear cut. I was running with 10 slaves, 100 Locust classes in my locustfile (because I need to hit 100 different hosts) and the minimum number of users I can run with is 501. 500 or less spawns zero users. It might also have to do with the spawn rate. The logs of each slave say "spawning 0 clients with hatch rate of 0.2 cl/sec" or something similar. |
We have 80 slaves in our set up and this is somewhat restrictive at times i.e. at times it would be nice step in finer jumps than 80 (of course I could kill some slaves, but that's a bit clunky)
The text was updated successfully, but these errors were encountered: