Beat the rush! Designing effective load tests for your web application
summary
Load tests focus on specifics: use Locust HTTP users or a playwright user to drive realistic browser or HTTP traffic, seed test data with Nemesis not two records, and introduce randomness in IDs and think in terms of concurrency not just total requests. Watch the 95th percentile and ramp users up; a climb at ~190 concurrent users often reveals a bottleneck. An obituary-site test holds up under peak load when designed this way.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:30Welcome
- 0:52Follow along
- 1:09Load testing and tea
- 2:18Load testing analogy
- 3:45Designing load tests
- 6:33Understanding your users
- 6:54Paths
- 7:47Timing
- 10:30Locust
- 11:12Locus script
- 13:02Playwright
- 14:28Django
- 15:39Common pitfalls
- 17:02Nemesis
- 18:08Test Question
- 19:05Cache
- 19:25Cache Stack
- 21:57Design your load test
- 23:24How to interpret the results
- 25:25Ramping up users
- 28:38Conclusion
related talks
45mBeat the rush! Designing effective load tests for your web application
26mLoad testing websites following the steps of a user journey
26mIntroduction to Load Testing
47mLoad Testing You Always Wanted
51mLoad Testing: How to Know Your Limits
46mLoad Testing Without Being Off the Mark
09mPerformance is the first UX challenge to consider
48mHow to not Crash in Prod, Load Testing Crash Course