Share this page

# Load generators

This section describes how to set up load generators for your scenarios.

In this topic:

## About load generators

When you execute a scenario, Controller distributes each Vuser in the scenario to a load generator. The load generator is the machine that executes the Vuser script, enabling the Vuser to emulate the actions of a human user.

Each Vuser script that runs on a load generator results in a single Vuser. Each load generator can run multiple Vuser scripts, thereby resulting in multiple Vusers. While these Vusers run, they create load on your system, enabling you to analyze your system under load.

## Create load generators

To create a load generator, you install the load generator software on a host computer. Load generators can be either Windows-based or Linux-based. For Docker platforms, you can use one of the available Dockerized load generator images (see Configure Dockerized load generators).

For details on how to install the appropriate load generator software, see the Install guide.

Note: The standalone load generator and standalone monitor over firewall (MOFW SA) cannot be installed on the same machine. However, the load generator can be used for monitoring purposes, the same way as the MOFW SA. Note that a single machine cannot be used simultaneously for both running Vusers and monitoring.

### Include load generators in a scenario

After you have installed the load generator software on a host computer to create a load generator, you can include the new load generator in a scenario. You use Controller to add the new load generator to a scenario.

To enable a scenario to develop significant load on a system, a typical scenario may include multiple load generators. You define and maintain the list of load generators that are available in a scenario. When you add a load generator to the list of load generators in a scenario, you define various attributes of the load generator, such as the platform on which the load generator runs. You can modify some - but not all - of these attributes after the load generator is created.

### Enable and deactivate a load generator

If a specific load generator is included in the list of load generators for a scenario, but is temporarily unavailable for a particular scenario run, you can deactivate the load generator instead of removing it permanently from the list. You can then enable the load generator if and when it becomes available.

### Connect/Disconnect a load generator

To manually connect or disconnect a load generator, on the Controller toolbar, click Load Generators.

Select a load generator in the list and click Connect/Disconnect.

If, during a load test, a load generator becomes disconnected from its network for a short period of time (for example, due to intermittent network connection issues), Controller can automatically reconnect to the load generator and continue running the load test. If the disconnection continues for longer than approximately two minutes, you must manually reconnect the load generator and rerun the load test.

## Use load generators with other products

The Windows installer package OneLG is a combined load generator installer. During installation, you select the relevant product, and the load generator is installed with the appropriate OpenText Professional Performance Engineering Agent configuration for that flavor.

Each load generator type has the following setup:

- OpenText Professional Performance Engineering. After load generator installation, by default the agent runs as a process (magentproc.exe).
- OpenText Enterprise Performance Engineering. After load generator installation, by default the agent runs as a service (agentservice.exe).

- OpenText Core Performance Engineering. Load generator installation includes defining configuration settings. After load generator installation, by default the agent runs as a service (not relevant for OpenText Core Performance Engineering processes).

After a load generator is installed, you have the option to switch the load generator to work with a different tool from the product family. This may involve reconfiguring load generator settings, using the following shortcut options available from the machine Start menu under OpenText Performance Engineering:

Product | Action | Start menu name
--- | --- | ---
OpenText Professional Performance Engineering | Define login parameters to use when switching from a manual process to a service. For details, see Agent Runtime Settings dialog box. | Agent Runtime Settings Configuration
OpenText Core Performance Engineering | Configure settings for the agent. For details, see the OPLG documentation in the Help Center. | Configure Load Generator
OpenText Performance Engineering | Switch the agent to run as a service. | Agent Service
OpenText Performance Engineering | Switch the agent to run as a manual process. | Agent Process

The actions required to switch load generator flavor are as follows:

Installed flavor | Use with Professional | Use with Enterprise | Use with Core
--- | --- | --- | ---
Professional | No action required | Switch to service | Configure agent
Enterprise | No action required | No action required | Configure agent
Core | No action required | No action required | No action required

Caution: When using OpenText Professional Performance Engineering, there are some specific protocols that require the agent to run as a process.

## Local versus cloud-based load generators

A load generator can be located on either a local computer or in the cloud. A scenario can include both local and cloud-based load generators. The procedure for defining and maintaining load generators is similar for local and cloud-based load generators. For details, see Add load generators to a scenario.

## Configure load generators

To create and run accurate real-life scenarios, you can configure numerous settings for each load generator that is included in a scenario. For details, see Add New Load Generator/Load Generator Information dialog box.

## View load generator status

Controller's Load Generators dialog box shows the status of each load generator in a scenario. The status of a load generator changes during a scenario run. For example, when you add a load generator to the list of load generators in a scenario, the load generator has the status Down. The status of the load generator changes to Ready when the load generator is connected to Controller and is available to run Vuser scripts, and then to Running while the load generator executes a Vuser script. For a full list of load generator statuses, see Load Generators dialog box.

## See also

- Agent processes
- Set up a load generator environment
- Add load generators to a scenario
- Known issues for load generators

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: