To reach the goal LoadView performs a series of iterations during Goal-Based Load Testing.

Each iteration includes the following steps:

  1. Measurements and analysis.
  2. Load adjustment stage (no measurements performed).

Measurements and analysis

During the stage, LoadView calculates the average response time of the stage – Avg. Duration of a transaction simulated on the target website at the current iteration – to set a target user load for the next test iteration.

To ensure accuracy, the device is executed several times during the stage. The number of executions during the stage is set by the Adjustment Rate parameter. Therefore, Avg. Duration is calculated for the total number of responses that equals the number of simulated users times the Adjustment Rate parameter.

Measurement stops when responses for all simulated user sessions are received.


Let’s say the number of simultaneous virtual users for the iteration is 100 users. Adjustment rate for the test is set to the default value of 3. 

Total number of responses = 100×3= 300.

LoadView sums up the response times of these 300 responses and then calculates the average to receive the Avg. Duration value.  

To calculate the load level for the next iteration the following formula is used :

User Load Transaction Goal per min x Avg.Duration

Load adjustment stage 

The stage is a time needed to reach the next level of user load. It may take time for LoadView Injectors Servers to reach the target load level (95% or more) but no more than 1 min. 

At least three iterations during no less than 10 minutes are necessary to finish a test successfully. If the goal is reached earlier than the specified duration time, the system will continue testing. 

At the start, you will be charged for the maximum number of virtual users specified while the test configuring.

If the goal is reached with the fewer number of users than pre-defined, the difference between the price paid for the maximum count and the price of the actual count will be refunded.