🏗️ Foundations · Days 1–6
Day 3: Think Time & Pacing
Objective
Add realistic think time between steps and compare throughput with and without it.
Scenario
Run your script with no think time. Note throughput. Add 3 seconds of think time. Re-run. The difference is what real users actually generate.
Metrics to Watch
When It Clicks
Removing think time inflates load that no real user generates.
Solution
In JMeter: add a Gaussian Random Timer (deviation 1000ms, constant delay 2000ms) inside your Thread Group after each sampler. Run once without it, note throughput. Add it and re-run. In k6: add `sleep(3)` at the end of your default function. A realistic think time of 2-5 seconds typically reduces throughput by 60-80% compared to a zero-think-time run - that reduction reflects reality, not a regression.
Reflection
What would happen if someone showed 'thousands of concurrent users' but with zero think time?
Deliverable
A script with configurable think time.
⚠️ 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.