Introduction to Load Testing
summary
Defines performance as 100 milliseconds and measures throughput by how many concurrent users an endpoint serves, using four concrete tests: load, stress, spike testing, and soak. Recommends K6 as a JS-scriptable tool, ~14–15 lines to define stages, core in Go, roughly 30–40 VUs per engine and ~1–5 MB RAM per virtual user so local runs top out near 100 virtual users. Describes replacing one large API call with three smaller endpoints and seeing a ~1 second improvement in average request duration.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:13Load testing origins
- 4:01What is load testing
- 5:26Performance basics
- 8:18Stress testing infrastructure
- 10:47Spike testing attacks
- 12:36Soak testing reliability
- 14:45K6 load testing tool
- 18:39K6 local testing limits
- 20:25Advanced K6 scenarios
- 21:52Cost and scalability
- 22:55Recommendations
related talks
26mTo see what others can not... You must climb the mountain, A Introduction to Load Testing
45mBeat the rush! Designing effective load tests for your web application
26mLoad testing websites following the steps of a user journey
47mLoad Testing You Always Wanted
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
30mBeat the rush! Designing effective load tests for your web application
09mPerformance is the first UX challenge to consider
45mFrom Functional Tests to Performance Tests: Robustum, an Implementation Example