-
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
master slave config, master not doing any work ? #211
Comments
That's correct. The master only collects and aggregates the stats reported by each slave node. |
thanks for clarification, so I guess if i have enough resources, I can start a few slave threads on the master too ? how many cpu cores should I reserve for master locust work ? something like master 8 cpu threads
slave 8 cpu threads
|
It's different for each case. However, for a load test to be reliable the tool that's doing the load test should never be allowed to be the limiting factor, so I would advise you to make sure that no slave or master node are close to reaching a resource cap. |
thanks seems even with 8 slaves + 4 slaves on master each locust process barely uses any cpu and memory resources between 1.7% and 3% cpu and 0.1% memory at 1000 users and hatch rate of 100 users over 12 slaves |
I have setup a master + slave Locust config and when I run a test, it seems the slave is the only one connecting to my target test site I am load testing ?
on target test site server i am checking netstat and it only shows the ip of the slave and nothing from master ? i tested with low 100 users and 100 user hatch rate
The text was updated successfully, but these errors were encountered: