Accelerate with confidence through AWS Distributed Load Testing
summary
Demo deploys AWS Distributed Load Testing (Apache JMeter on ECS Fargate) to simulate up to ~600 virtual users, and uses CloudWatch Synthetics canaries plus X-Ray traces to diagnose failures. A simple pet‑store API collapses when concurrent requests exceed ~50 because RDS connections hit the 350 limit; CPU and memory stay low. Test run costs under $1 for ~20 minutes, X‑Ray remains free under 10k traces, and the fix suggested is to reduce connections or add RDS proxy.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:39Confidence through testing
- 5:41Types of performance testing
- 8:59AWS Distributed Load Testing
- 13:11Synthetic monitoring
- 15:25Diagnosing with X-Ray
- 16:56Pet store demo setup
- 18:01Running load test
- 23:34Finding the bottleneck
- 25:54Key takeaways and resources
related talks
19mLoad Testing AWS Serverless Architectures with Serverless
57mLast- und Performancetests in der Cloud?!
01h 08mPerformance testing in the cloud
09mPerformance is the first UX challenge to consider
52mLoad testing distributed web services
34mChaos in the cloud
47mLoad Testing You Always Wanted
35mAWS Lambda performance tuning