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.

Sign up for GitHub

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

Jump to bottom

Issue with locust framework. Wondering if anyone has seen this behavior before. #8

Closed
yurko006 opened this issue Nov 17, 2017 · 1 comment
Closed

Issue with locust framework. Wondering if anyone has seen this behavior before. #8

yurko006 opened this issue Nov 17, 2017 · 1 comment

Comments

@yurko006
Copy link

locustio/locust#690
@abhiksingh
Copy link
Contributor

This seems like an issue with running Locust on T2 instance family has a burstable CPU model which is likely the culprit for the behavior. For more information, see https://aws.amazon.com/ec2/instance-types/#burst.

For sustained workloads such as load testing, I'd recommend the C4 or C5 instance family.

Closing as this isn't an issue with the sample.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abhiksingh @yurko006