Share this page
OPLG requirements
On-premises load generators (OPLGs) allow you to load test your secure applications. This topic describes the basic requirements and points to consider before installing an on-premises load generator.
Prepare for your installation
On-premises load generators of the current version, and up to two versions back are supported. For details, see Support Matrix.
Tip: We recommend that you do the following:
-
Install on-premises load generators on dedicated machines that do not contain or give access to sensitive information, and on machines that are not running any OpenText performance or functional products.
-
Thoroughly review your network topology and access levels.
Vuser balancing
With Vuser balancing, Vusers are distributed 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.
Vuser balancing can be turned off upon request. To deactivate the balancing for your tenant, submit a service request.
Examples
The following table provides examples of Vuser balancing.
| Examples | Description |
|---|---|
| With Vuser balancing |
Let's say you have a test with 15 TruClient Vusers and 2 on-premises load generators, where the maximum number of Vusers for TruClient load generator is 15. A single load generator is allocated, and the 15 Vusers run on this load generator. When running a similar test with 20 TruClient Vusers, 2 load generators are allocated and the Vusers are distributed equally, 10 and 10, over the 2 machines. The balancing improves the utilization of the resources, such as network bandwidth, CPU, and memory. As a result, Vuser execution is faster and there is a smaller chance of receiving usage alerts on the load generator machine. |
| When Vuser balancing is turned off |
To illustrate the Vuser distribution when Vuser balancing is turned off, we'll use the above example with 20 TruClient Vusers and 2 on-premises load generators. Two load generators are allocated and the maximum number of Vusers, 15, is assigned to the first load generator. The remaining 5 Vusers are then assigned 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 is not applied when:
- If the Vusers are running different protocols. Only Vusers using the same protocol can be run 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 Enable manual Vuser distribution for on-premises load generators option is selected. For details, see Load generators.
- Advanced mode settings scheduling is activated for a test. For details, see Advanced mode settings.
See also:
