-
Notifications
You must be signed in to change notification settings - Fork 106
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
API load testing setup #4327
Comments
1 task
Closed
6 tasks
lbeaufort
changed the title
After Aurora migration, measure "fallover point" for number/complexity of requests
API load testing setup
May 5, 2020
10 tasks
We should also let the team and cloud.gov know (ideally a week beforehand) which day we plan to test. Reference: https://cloud.gov/docs/compliance/pentest/ |
Parsing script:
|
In the console:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html |
There were some issues with formatting the requests, so I also did some testing with the normal locust setup. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Action item from #4314
Need to know what the system can handle before it "falls over". Need to know what the load was on April 15, for example.
Completion criteria:
Technical steps
Prepare the "locusts"
Set up environment
prod
now that we're using Aurora. How many clusters, PR to terraform, check with DB team on timing, etc.DEV (1 master - 1 replica)
STG (1 master - 1 replica)
PRD (1 master - 4 replica)
(Change it manually during the test make it much easier than going thru terraform). Make sure to scale it down after the test to minimize cost.
Should test 2 vs. 4 clusters
stage
as-isCommunicate
The text was updated successfully, but these errors were encountered: