Stress Testing as a Culture
summary
Startup runs po potatoes through a stress test with loader iio, gets 15 requests/minute but only 3 succeed and average response time is ~10s, so goals change to 5 requests/sec (300/min) and −500ms reduction. Team adds DB indexes, restructures relationships, moves work to background jobs, rewrites hot code and implements aggressive caching, integrates automated stress tests into deployment; next test shows 299/300 requests at 627ms, yet the app still goes down on game day.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:45Stress Testing as a Culture
- 15:50Mobile First
- 17:50BBC
- 19:10Types of Testing
- 21:25Tools
- 23:55Kuchar
- 25:55World Cup
- 28:55Performance
- 30:25Wrap up
related talks
28mStress Testing in Production: The New York Times Engineering Survival Guide
26mHow We Prepped Our Infrastructure for a Super-Bowl Sized Traffic
44mPerformance Testing for Modern Apps
25mGame time: A playbook to (unsuccessfully) 10x in a week and (successfully) 10x in a year
21mCrunching Millions of Requests for Breakfast: A Tale of Performance Testing Prowess
33mHow much pressure can your app handle - Performance testing with Ruby
46mChaos Experiments - Datacenter Stress Testing
19mKeeping High-Traffic Systems Running When Things Go Wrong