LoadView Goal-Based Test is a smart testing tool that provides testing against a target number of transactions and automatically adjusts all the necessary test parameters as user load and test scenario. A goal-based load type is useful when you have already identified the limiting level of your required throughput and need to ensure that your performance goal is met.
How to find your Transaction goal
Throughput is the number of transactions per given period of time. Transaction goal is calculated as the number of transactions per minute. So you need to estimate the number of transactions per any period of time, calculate the number of minutes in this time period, and then divide the number of transactions by the number of minutes.
Let’s assume, your website is expected to have 600 logins per 1-hour. It is equal to 600 login transactions per 1 hour. An hour contains 60 minutes.
To calculate the web site throughput you need to divide 600 transactions by 60 minutes. The resulting value of 10 is your goal number of transactions per minute Transaction goal.
How it works
To reach the goal LoadView performs a series of iterations during a load test.
Each iteration includes the following steps:
- Measurements and analysis.
- Load adjustment stage (no measurements performed).
Measurements and analysis
During the stage, LoadView calculates the average response time – Avg. Duration of the response 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.
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.
Configuring and starting a test
While configuring the test you can use recommended values of the test parameters or specify custom values according to your goals. You can also start the test with default Transaction Goal per min as well as use default VUD.
To configure the test with custom settings:
- Enter your goal throughput in the Transaction Goal per min box in minutes. Automatically adjusted stress test parameters will be calculated and appear under the respective boxes in the Recommended field.
- To set a recommended value for a parameter, point to the recommended value field, and click Apply Value. If you need to update the recommended values, click Recommend Values.
- Specify custom VUD in the Number of Virtual Users per Load Injector Server box or use calibrated value by clicking Recommend VUD, and then point to the recommended value field and click Apply Value.
- To test your website from more than one geo-zone, if necessary, configure zone settings.
- Check the test summary and validation result in the footer. If validation failed fix errors before starting a test.
- Click Run Test, and to receive a notification on the test start, on the Stress Test Summary page, provide your email in the Notification Email section. Сlick Run Test again.
- Read the user agreement, enter your name in the corresponding box and select I agree.
- Click Start. You will be redirected to the Stress Test Report page where the progress of the test execution will be presented.
Once you have run the test, it will start within 10 minutes (up to 1 hour depending on the region selected). The system notifies you with the corresponding message on the report page after the test completed.
When the test finished, you can view test results on the Stress Test Report page. To find if the Transaction goal was reached successfully, check the Transactions per minute chart. Also, it is recommended to check the Session Report for errors detected.