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

Unusual behavior from graphs #690

Closed
yurko006 opened this issue Nov 16, 2017 · 5 comments
Closed

Unusual behavior from graphs #690

yurko006 opened this issue Nov 16, 2017 · 5 comments

Comments

@yurko006
Copy link

yurko006 commented Nov 16, 2017

Description of issue / feature request

I am running locust.io on aws with t2.micro instances. One master and two slaves on Elastic Beanstalk. I am getting some strange behavior when it comes to the graphs.

Expected behavior

Would like to see a smooth continuous graph such as the one below. NOTE: This was running off of a Mid 2015 MacbookPro locally, non distributed.

screen shot 2017-11-08 at 2 29 05 pm

screen shot 2017-11-08 at 2 29 11 pm

Actual behavior

This is what it looks like when running on Elastic Beanstalk.

screen shot 2017-11-16 at 3 36 56 pm

Environment settings (for bug reports)

  • OS: 64bit Amazon Linux 2017.09 v2.6.0 running Java 8
  • Locust version: 0.8.2
@heyman
Copy link
Member

heyman commented Nov 17, 2017

That does look weird. It's hard to debug without a way to reproduce it. Does it happen consistently? Have you tried with the Locust master branch (there been some changes to the stats & chart code). Do you use python 3 or 2?

@yurko006
Copy link
Author

yurko006 commented Nov 17, 2017

I used this repo as an example of how to deploy this framework on Elastic Beanstalk with some changes as to the framework version and instance type I am running on. It happens every time I run the code. What is also interesting is that I am seeing the number of slaves fluctuate between one and two when I run a test with the aforementioned configuration. I am running locust 0.8.1 which I grab from pip. To be honest, I am not completely sure how to check which python version it is running. Is there a version which the framework defaults to, or is there an easy way which I can check which version the framework is using?

@heyman
Copy link
Member

heyman commented Nov 17, 2017

Hmm, I haven't used Elastic Beanstalk. Could it be related to some autoscaling mechanism that is used?

Also, did you see the following in Readme of the repo you linked:

image
?

You should be able see the Python version simply by running python --version, if the Elastic-Beanstalk environment lets you do that.

@abhiksingh
Copy link

I believe this may be related to the fact that locust is CPU intensive and t2.micro instances only allow you to burst to full CPU for 6 minutes/hour. See https://aws.amazon.com/ec2/instance-types/#burst for more details.

@cgoldberg
Copy link
Member

@abhiksingh interesting!

@yurko006 yurko006 closed this as completed May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants