Iteration Calculator

Free Tool

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 Testing

User load.

Time to complete one iteration.

Delay between two iterations.

Sum of all the think times used in the script.

* Required fields. Results update automatically as you type.

Results

Enter your values to see the result.


What is the Iteration Calculator?

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.

How it works

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.

Formula to calculate iterations per hour

Iterations per Hour (per user) = 3600 ÷ (Response Time + Pacing + Think Time) Total Iterations per Hour = Iterations per Hour × Users

Where:

  • 3600Number of seconds in one hour.
  • Response TimeEnd-to-end time to complete one iteration, in seconds.
  • PacingDelay between two iterations, in seconds (0 if none).
  • Think TimeSum of all think times in the script, in seconds (0 if none).
  • UsersNumber of concurrent virtual users (threads).

Example of iteration calculation

A search-and-browse script runs with 25 users.

Inputs

  • Users = 25
  • Response Time = 10 seconds
  • Pacing = 5 seconds
  • Think Time = 5 seconds

Step-by-step

  1. Time per iteration = 10 + 5 + 5 = 20 seconds
  2. Iterations per Hour (per user) = 3600 ÷ 20 = 180
  3. Total Iterations per Hour = 180 × 25 = 4500

Result: Each user completes 180 iterations per hour, or 4,500 iterations per hour for all users combined.

Common mistakes to avoid

  • 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.


Need advanced performance testing?

Run this scenario at real scale with Baseline11's distributed load testing platform.

Explore Baseline11