Estimate the number of script loops or iterations each virtual user will execute per hour during the test, based on total duration, think time, response time, and pacing.
Performance TestingUser load.
Time to complete one iteration.
Delay between two iterations.
Sum of all the think times used in the script.
Enter your values to see the result.
The Iteration Calculator estimates how many times each virtual user will run your test script per hour, and the total for all users combined. An iteration is one full pass through the script, for example log in → search → add to cart → log out. Knowing the iteration count helps you check that the test matches the business volume you are modelling.
Each iteration takes response time + pacing + think time seconds to complete. Dividing an hour by that per-iteration time gives how many iterations one user runs per hour; multiplying by the number of users gives the total across the whole test.
Where:
A search-and-browse script runs with 25 users.
Inputs
Step-by-step
Result: Each user completes 180 iterations per hour, or 4,500 iterations per hour for all users combined.
Ignoring pacing and think time, which inflates the estimated iteration count well above what the test will actually produce.
Using response time from a lightly-loaded baseline instead of the response time expected under target load.
Comparing total iterations across tests with different user counts without checking the per-user rate too.
Run this scenario at real scale with Baseline11's distributed load testing platform.