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

master slave config, master not doing any work ? #211

Closed
centminmod opened this issue Dec 2, 2014 · 4 comments
Closed

master slave config, master not doing any work ? #211

centminmod opened this issue Dec 2, 2014 · 4 comments

Comments

@centminmod
Copy link

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

netstat -ntu | awk ' $5 ~ /^(::ffff:|[0-9|])/ { gsub("::ffff:","",$5); print $5}' | cut -d: -f1 | sort | uniq -c | sort -nr
@Jahaja
Copy link
Member

Jahaja commented Dec 2, 2014

That's correct. The master only collects and aggregates the stats reported by each slave node.

@Jahaja Jahaja closed this as completed Dec 2, 2014
@centminmod
Copy link
Author

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

locust -H http://wordpress7.centminmod.com -f /home/locustfiles/locustfile_wp7.py --master &

for s in $(seq 4); do locust -H http://wordpress7.centminmod.com -f /home/locustfiles/locustfile_wp7.py --slave --master-host=masterip & done

slave 8 cpu threads

 for s in $(seq 8); do locust -H http://wordpress7.centminmod.com -f /home/locustfiles/locustfile_wp7.py --slave --master-host=masterip & done

@Jahaja
Copy link
Member

Jahaja commented Dec 2, 2014

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.

@centminmod
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants