Measure the actual throughput of your test by calculating how many transactions are processed per second over the test duration.
Performance TestingUser load.
Time to complete one iteration.
Get this value from the performance test script.
Delay between two iterations.
Sum of all the think times used in the script.
Enter your values to see the result.
The TPS Calculator estimates the transactions per second (TPS) and transactions per hour (TPH) your load test will generate. TPS is the most common way to express throughput in performance testing, so this calculator is useful both before a test, to check that your script and user count will hit the target, and after a test, to sanity-check the throughput you saw.
Each user completes one iteration every (response time + pacing + think time) seconds, and produces a fixed number of transactions per iteration. Multiplying users by transactions and dividing by the time per iteration gives the sustained transaction rate.
Where:
A banking script logs in, checks the balance, views a statement, makes a transfer and logs out: 5 transactions per iteration.
Inputs
Step-by-step
Result: The test produces about 50 TPS, or 180,000 transactions per hour.
Counting "iterations per second" when the script actually runs multiple transactions per iteration — use the transactions field to get real TPS.
Leaving pacing and think time both at 0 when your script genuinely has delays, which overstates achievable TPS.
Comparing TPS across scripts with different transaction counts per iteration without normalizing first.
Run this scenario at real scale with Baseline11's distributed load testing platform.