How to not Crash in Prod, Load Testing Crash Course
summary
Explains how to turn vague requirements like 1,000 users for 1 hour into concrete tests by choosing open vs closed workload models, shaping injection profiles, and measuring percentiles such as p90/p99 instead of averages. Describes pitfalls: TLS handshakes, ephemeral port exhaustion, and unrealistic global connection pooling that hides client-side failures. Shows Gatling-based tests using CSV feeders, composable scenarios, and CI runs, and contrasts free open-source generators with an enterprise SaaS for orchestration and reporting.
AI-written summary · about
chapters (14)
- 0:00Start
- 7:18What load testing is NOT
- 11:18Stateful
- 12:00Creating scenarios
- 13:11Infrastructure and Network
- 21:21Open System Model
- 25:49Capacity Test
- 26:27Stress Test
- 27:13Smoke Test
- 29:19Test Data
- 30:55How to NOT Measure
- 41:43Load Test As Code
- 46:47Gatling for Enterprises
- 47:28Gatling references
related talks
46mLoad Testing Without Being Off the Mark
45mBeat the rush! Designing effective load tests for your web application
47mLoad Testing You Always Wanted
30mBeat the rush! Designing effective load tests for your web application
27mTesting Before You Scale & Making Friends While You Do It
31mKill! Kill! Die! Die! Load Testing With A Vengeance
50mFrom Load Testing to Reliability Engineering: Making Performance Testing Predict Production Behavior
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things