📈 Load Patterns · Days 7–12
Day 11: Step Load
Objective
Increase load in fixed steps and record throughput at each plateau.
Scenario
Run 10 users for 5 min. Then 20 for 5 min. Then 30, 40, 50. Record throughput at each step. Plot throughput vs users.
Metrics to Watch
When It Clicks
Throughput stops rising while users keep increasing = saturation.
Solution
Use JMeter's Ultimate Thread Group plugin or five sequential Thread Groups each with a different user count and 5-minute duration. Record throughput from the Aggregate Report at each step. In k6: use stages with `{ duration: '5m', target: 10 }` increments. Plot users vs throughput in a spreadsheet. The step where throughput stops increasing (or drops) while users rise is saturation. Little's Law: throughput = concurrency / response time - when response time climbs faster than concurrency, throughput plateaus.
Reflection
At what user count did throughput stop scaling? What resource hit its limit first?
Deliverable
A step-load script with per-step throughput comparison.
⚠️ Never run load tests against infrastructure you do not own or have explicit written permission to test. Always use a dedicated test environment. Unauthorized load injection can cause outages, trigger legal liability, and violate terms of service.