You can install an on-premises load generator to load test your secure applications.
Prepare for your installation
LoadRunner Cloud supports on-premises load generators of the current version, and up to two versions back. For details, see On-premises load generators (OPLGs).
We strongly recommend that you do the following:
Install the LoadRunner Cloud On-premises Load Generator on a dedicated machine that does not contain or give access to sensitive information.
Install the LoadRunner Cloud On-premises Load Generator on a machine that is not running any Micro Focus performance or functional products.
Thoroughly review your network topology and access levels.
Install and configure a load generator
Click the relevant link to begin working with your on-premises load generators.
- Install an on-premises load generator on Windows
- Deploy a Docker container for Linux
- On-premises load generator configuration tool
With Vuser balancing, LoadRunner Cloud tries to distribute Vusers equally across multiple on-premises load generators allocated for the test run.
The number of on-premises load generators required for a specific test is determined in runtime during the test initialization. For example, let's say you have a test with 15 TruClient Vusers and two on-premises load generators, where the maximum number of Vusers for TruClient load generator is 15. LoadRunner Cloud will allocate a single load generator, and the 15 Vusers will run on this single load generator. When running a similar test with 20 TruClient Vusers, LoadRunner Cloud will allocate two load generators and will distribute the Vusers equally, 10 and 10, over the two machines.
The balancing improves the utilization of the resources, such as network bandwidth, CPU, and memory. As a result, Vuser execution will be faster and there are less chances that you will receive usage alerts on the load generator machine.
Vuser balancing can be disabled upon request. To disable the balancing for your tenant, open a support ticket. To illustrate the Vuser distribution when Vuser balancing is disabled, we'll use the above example with 20 TruClient Vusers and two on-premises load generators. LoadRunner Cloud will allocate two load generators and assign the maximum number of Vusers, 15, to the first load generator. It will then assign the remaining 5 Vusers to the second load generator. In this case, the first load generator may become overloaded while the second machine would remain idle.
Note: Vuser balancing applies to Vusers—not scripts. Vuser balancing will not be applied when:
- Advanced mode settings scheduling is enabled for a test.
- If the Vusers are running different protocols. Only Vusers using the same protocol can be executed on the same on-premises load generator.
- If a protocol is limited to specific load generators, for example, TruClient is limited to Windows on-premises load generators.
- When the Define general test settings option is enabled.