Once the Transaction Goal has been set, LoadVew automatically suggests the starting and the maximum number of users, and the test duration necessary to reach the goal. We strongly advise initiating the test with these recommended settings.

  • Start with User Load

The parameter defines the number of virtual users required to achieve the desired Transaction Goal at the start of a load test. The recommended value for this parameter is determined based on the response time (Validation Session Duration) measured for the single-user test run executed during test validation:

Starting User Load = Transaction Goal per min x Validation Session Duration

  • Maximum Concurrent Virtual Users

The parameter defines the maximum number of Load Injector servers required to execute the test. The value is calculated based on the Start with user load value and reflects a buffer in the Start with user load parameter:

Max. Simultaneous Virtual Users = Starting User Load x 3

Maintaining a buffer in the Start with user load parameter helps ensure the desired Transaction Goal per minute is matched, even if server response times increase unexpectedly during a load test.

  • Test Duration (in minutes)

Based on the set test parameters, the system recommends a “minimum sufficient duration for accurate results,” assuming that your server average response time (Avg. Response Duration) does not significantly differ from the response time value received during test validation.

To receive accurate test results, conducting a minimum of three test cycles is required. Each cycle duration is defined by the duration of a complete test execution by a single virtual user and the Adjustment Rate parameter. Therefore, changing the Adjustment Rate also affects the recommended Test Duration.

The recommended Test Duration is calculated as:

Test Duration = (Adjustment Rate + 1) × Avg. Response Duration × 3

DO NOT use the Adjustment Rate parameter to change the Test Duration value.

  • Adjustment Rate

This parameter specifies the number of complete test script (test sample) executions by a single virtual user required to define the duration of a single test cycle for accurate test results.

Let’s say the number of concurrent virtual users for the cycle is 100 users. Adjustment Rate for the test is set to the default value of 3.

Required total number of responses for the current cycle = 100×3 = 300.

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

Expert Tips

Tip 1. Adjust the value of the Maximum concurrent users in accordance with your server performance

If you anticipate that your server response duration under load may increase more than three times compared to the duration obtained during test target validation, you should manually increase the Maximum number of concurrent virtual users above the recommended level.

Note that an increase in the Maximum number of concurrent virtual users may lead to an increase in the number of Load Injectors and the cost of load testing.

Tip 2. Make sure your test duration is sufficient for accurate test results

The system automatically calculates and recommends a minimally sufficient Test Duration to receive accurate results. We advise against setting the Test Duration value below the default recommendation.

If you set your test duration shorter than a single test cycle, the stress test will conclude at the specified load Test Duration, leading to inaccurate test results.

If you require a longer stress test, set the desired test duration accordingly.

Note that an increase in the Test Duration parameter may lead to an increase in the cost of load testing.

Tip 3. Do not change Adjustment Rate until it’s recommended by the LoadView team

The minimum recommended value for the Adjustment Rate is 3, as this provides an optimal balance between accuracy and test performance.

Increasing the Adjustment Rate can enhance measurement precision in some specific cases. However, it will also extend the test duration and potentially increase costs. Therefore, if your objective is solely to lengthen the test duration, it is advisable to adjust the Test Duration parameter directly, rather than modifying the Adjustment Rate. Otherwise, please create a support ticket for your test scenario review before changing the default Adjustment Rate value.