How the estimate works
Section titled “How the estimate works”Little’s Law: concurrency ≈ arrival rate × cycle time. Cycle time is response time + think time.
threads ≈ ceil(target_RPS × (response_time_ms + think_time_ms) / 1000)Leave think time at 0 for busy threads (no timer). Copy Thread Group writes the fields you paste into JMeter; add a Constant Timer when think time is greater than zero.
Example
Section titled “Example”| Target RPS | Avg response time | Think time | Recommended threads |
|---|---|---|---|
| 50 | 200 ms | 0 | 10 |
| 50 | 200 ms | 800 ms | 50 |
| 100 | 500 ms | 0 | 50 |
What this does not include
Section titled “What this does not include”- Pacing that holds a fixed iteration rate (Constant Throughput Timer)
- Injector CPU, bandwidth, and listener overhead
- Server saturation (response time rises under load; re-measure)
- Splitting load across engines; see Remote Testing
Recommended workflow
Section titled “Recommended workflow”- Measure average response time with a small pilot.
- Use this calculator for an initial thread count and ramp-up.
- Run CLI mode (
jmeter -n -t plan.jmx -l results.jtl) without View Results Tree. - Compare achieved throughput in the HTML dashboard.
- Scale out with distributed testing when one injector is saturated.