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

rps bottleneck #313

Closed
ghost opened this issue Aug 5, 2015 · 3 comments
Closed

rps bottleneck #313

ghost opened this issue Aug 5, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Aug 5, 2015

I am running a GET on www.google.co.uk on a m3.xlarge (4 CPUs, 15GB RAM (high network)). I've input 2000 users, but I am unable to reach much more than 600 r/s when total CPU is less than 25% and used RAM is around 3GB. I wonder what the bottleneck is?

@vividhsv
Copy link

vividhsv commented Aug 5, 2015

are you running in distributed setup....?

If no, you should run in distributed setup.Since there are 4 CPUs you could run 3-4 slaves so that all the CPUs are used.

If you are in standalone mode you will end using only one 1CPU to its max (100%). You can also see it in your stats 25% of total CPU is like 100% of one CPU among the 4 CPUS. So basically other 3 CPU's are not being used.

@ghost
Copy link
Author

ghost commented Aug 6, 2015

HI @vividhsv

I had no idea that Locust was CPU-bound, but you are exactly right. Thanks very much.

@ghost ghost closed this as completed Aug 6, 2015
@cgoldberg
Copy link
Member

careful.. running 600 rps against Google is essentially a DDOS attack.

This issue was closed.
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