Understanding Throughput
How we calculate. Throughput (req/s) = successful requests ÷ test duration in seconds. The form uses the same arithmetic as the worked examples on this page. See our methodology and accuracy policy.
Real-world scenario: A typical Throughput case uses successful requests 180000 and duration (seconds) 600. Enter the same figures below to reproduce the worked path.
What is Throughput?
Throughput is a core load-test KPI. Pair it with error rate and response time—high throughput with rising errors is not a win.
- Count successes only unless you explicitly report attempted throughput
- Steady-state windows beat full-run averages that include ramp-up
- State units clearly (req/s, txn/min, messages/s)
The Formula
Worked Example
Common Use Cases
- Load tests: report sustained capacity
- SLA talks: compare measured vs target TPS
- Tuning: track throughput after config changes
Pro Tips
- Exclude warm-up from the duration window
- Watch saturation when throughput plateaus while latency climbs
- Separate read vs write workloads when patterns differ
Limitations: Throughput figures are educational performance-testing aids—not contractual capacity guarantees. Validate with calibrated load tools and production telemetry.
FAQ
Should failed requests count?
Usually no for success throughput. Report attempted rate separately if needed.
Req/s vs transactions/s?
Same formula—change only the unit label to match what you counted.
Authoritative References
For performance and quality engineering context, consult:
- ISTQB — performance testing syllabus topics
- W3C Navigation Timing — browser performance timing
- CMG / capacity forums — capacity and performance practice communities