Share this page

# Configure Controller options

This topic describes how to configure global settings for the Controller, monitors, runtime settings, timeouts, and debug information for all your LoadRunner Enterprise projects.

In this topic:

## About the Controller

The Controller is the manager of a performance test that receives the scripts, their runtime settings, and a list of load generators to use. The Controller issues instructions to the load generators including which scripts to run, how many Vusers to run per script, and the time at which to start running the Vusers.

During the performance test, the Controller displays online monitoring information. At the conclusion of the test run, the Controller collates the data for analysis.

Before you run a performance test, you can configure load generator and Vuser options for all your performance tests in the project. Although the default settings correspond to most environments, you can modify the settings to customize the test behavior.

Note: The settings apply to all future test runs in the project and generally only need to be set once. The settings apply globally to all the load generators in a performance test.

Back to top

## Configure monitor run options

This section describes how to activate the Transaction monitor, configure the behavior of the transaction data, and set the data sampling rate, debugging, and frequency settings for the online monitors.

1. In LoadRunner Enterprise, click Open the navigation toolbar and select Controller Options (under More Tools).

2. Select the Monitors tab.

3. Configure the monitor run options as required:

   UI Elements | Description
   --- | ---
   Transaction Data | Configures the behavior of data for the Transaction, Data Point, and Web Resource online graphs. Enable Transaction Monitor. Select this option to activate the online Vuser Transaction monitor to begin monitoring transactions at the start of a test run. Sample information at frequency <>. Select the frequency, in seconds, at which the online monitor samples the data to produce the Transaction, Data Point, and Web Resource online graphs. The higher the frequency, the less network traffic there is. The data is averaged for the frequency period defined, and only one value is sent to the Controller. Default value: 5 seconds. Tip: For a small test, use a frequency of 1. For a large test, use a frequency of 3 - 5. Note: You cannot modify these settings during a test run; you must stop the test run before deactivating the monitor or changing its frequency.
   Server Resource Monitors | Configures the behavior of the Server Resource monitors. Data Sampling Rate. The period of time (in seconds) between consecutive data sampling. By default, the online monitor samples the data at intervals of three seconds. If you increase the sampling rate, the data is monitored less frequently. This setting applies to all graphs. Note: The sampling rate configured here is applied to all server monitors that you subsequently activate. It is not applied to server monitors that have already been activated. To apply the new sampling rate to activated server monitors, save your performance test and reopen it. Each type of monitor has a different minimum sampling rate. If the default sampling rate, or the rate set here is less than a monitor's minimum sampling rate, the monitor samples data at its minimum sampling rate. For example, the minimum sampling rate for the Oracle Monitor is 10 seconds. If the data sampling rate set here is less than 10 seconds, the Oracle Monitor continues to monitor data at 10 second intervals.
   Debug | Display Debug Messages. The online monitor provides debugging capabilities. Select this option to display the debug messages in the Output window. Debug level. For the Network monitor, you can indicate the debug (detail) level of messages sent to the log, ranging from 1-9.

Back to top

## Configure runtime settings

This section describes how to configure runtime settings for your tests relating to Vuser quotas, stopping Vusers, and random sequence seed, to prevent system overload, and to control the way in which Vusers stop running.

1. In LoadRunner Enterprise, click Open the navigation toolbar and select Controller Options (under More Tools).

2. Select the Run-Time Settings tab.

3. Configure the runtime settings as required:

   UI Elements | Description
   --- | ---
   Vusers Quota | Vuser quotas prevent your system from overloading. The Vuser quotas apply to Vusers on all load generators. Number of Vusers that may be initialized simultaneously on all load generators. Limits the number of Vusers initialized at one time (when you send an Initialize command). Default value: 999
   When Stopping Vusers | Controls the way Vusers stop running when you manually stop a test run: Wait for the current iteration to end before stopping. (Default option) The Vuser completes the iteration it is running before stopping. The Vuser moves to the Gradual Exiting status and exits the test run gradually. Wait for the current action to end before stopping. The Vuser completes the action it is running before stopping. The Vuser moves to the Gradual Exiting status and exits the test run gradually. Stop immediately. The Vuser stops running immediately, moving to the Exiting status and exits the test run immediately.
   Random assignment mode for file-type parameters | Use random sequence with seed. Enables you to set a seed number for random sequencing. Select this option if you discover a problem during the test run and want to repeat the test using the same sequence of random values. Use seed <#>. Each seed value represents one sequence of random values used for test execution. Whenever you use this seed value, the same sequence of values is assigned to the Vusers in the test. This setting applies to parameterized Vuser scripts using the Random method for assigning values from a data file. It also affects the random percentage of recorded think time (see information about the Run-Time Settings dialog box in the Virtual User Generator Help Center.

Back to top

## Configure timeout settings

This section describes how to set timeouts for various LoadRunner Enterprise commands and for transferring files. When a command is issued by the Controller, you can set a maximum time for the load generator or Vuser to execute the command. If the command is not completed within the time limit, the Controller issues an error message.

1. In LoadRunner Enterprise, click Open the navigation toolbar and select Controller Options (under More Tools).

2. Select the Timeouts tab.

3. Configure the timeout settings as required:

   UI Elements | Description
   --- | ---
   Command Timeout (seconds) | Enable timeout checks. Enables load generator and Vuser timeout checks described below. If this option is not selected, LoadRunner Enterprise waits an unlimited time for the load generators to connect and disconnect, and for the Initialize, Start Vusers, Duration, and Stop Vusers actions to be executed. Load Generator. Load generator timeout limits: Connect operation (sec). The amount of time (in seconds) that elapses before connecting to any load generator. If a connection is not successful within this time, the status of the load generator changes to Failed. Default connection timeout: 30 seconds Disconnect operation (sec). The amount of time that elapses before disconnecting from any load generator. If the load generator does not disconnect within this time, the status of the load generator changes to Failed. Default disconnection timeout: 120 seconds Vusers. Vuser timeout limits: Init stage (sec). The timeout value for the Initialize action. Default time limit: 180 seconds Run stage (sec). The timeout value for the Start Vusers action. Default time limit: 120 seconds Pause stage (sec). The timeout value for the Duration action. Default time limit: 120 seconds Stop stage (sec). The timeout value for the Stop Vusers action. Default time limit: 120 seconds Note: Calculations consider the number of active Vusers and their influence on the timeout values. For example, 1000 Vusers trying to initialize take much longer than 10 Vusers. An internal value is added to the specified timeout value based on the number of active Vusers.
   Transfer scripts to load generators during test initialization stage timeout (Sec) | The time, in seconds, that script files must be transferred to the load generators during the test initialization stage before the timeout is reached. If this timeout is reached, the test fails and the Controller issues an error message. Default time limit: 900 seconds (15 minutes) Maximum value: 18000 seconds (5 hours) Minimum value: 60 seconds Note: This setting is only relevant when the Transfer scripts to load generators during test initialization stage option is selected in Test Options (see Configure general test options). Transferring scripts to load generators during test initialization stage is not compatible when using NV Insights.

Back to top

## Configure debug information settings

This section describes how to select the type of information you want to trace during test runs. According to the selection here, trace files are created and are used to gather information for debugging purposes.

1. In LoadRunner Enterprise, click Open the navigation toolbar and select Controller Options (under More Tools).

2. Select the Debug Information tab.

3. Configure the timeout settings as required:

   UI Elements | Description
   --- | ---
   Enable the following traces | The trace flags related to performance testing problems that you are encountering: General. Performs a general trace during the test run. File Transfer. Traces problems with the transfer of files during the test run. Incoming communication. Traces incoming communication during the test run. Outgoing communication. Traces outgoing communication during the test run. Note: The LoadRunner Enterprise agent and the Controller create some temporary files that collect information such as the parameter file sent to the Vuser, the output compilation file, and the configuration file. The LoadRunner Enterprise agent files are saved in brr folders in the TMP or TEMP directory of the agent machine. The Controller files are saved in lrr folders in the TMP or TEMP directory of the Controller machine. At the end of the test run, all of these files are automatically deleted.

Back to top

## Configure IP spoofing and advance warning settings

This section describes selecting a mode for allocating multiple IP addresses when IP spoofing is enabled. It also enables you to display advanced warnings in the Performance Test Designer Window.

1. In LoadRunner Enterprise, click Open the navigation toolbar and select Controller Options (under More Tools).

2. Select the General tab.

3. Configure the general settings as required:

   UI Elements | Description
   --- | ---
   Multiple IP Address Mode | The Controller can allocate an IP address in one of the following ways: IP address allocation per process. Allocates IP addresses per process. IP address allocation per thread. Allocates IP addresses per thread, resulting in a more varied range of IP addresses in a test run. Note: Web Vusers require IP address allocation per process. WinSock Vuser IP addresses can be allocated per thread or per process.
   Advanced Warnings | Select to display advanced warnings in the Messages pane of the Performance Test Designer window.

Back to top

## Configure collate result settings

This section describes how to specify the Controller behavior related to collation of the run results.

Note: For details on collating run results for a test, see Collate run data.

1. In LoadRunner Enterprise, click Open the navigation toolbar and select Controller Options (under More Tools).

2. Select the Collate Results tab.

3. Configure the collate settings as required:

   UI Elements | Description
   --- | ---
   Output Message Database | Add SqliteDb.db to RawResults.zip if it is smaller than RawResults.zip size (MB). Collator process adds SqliteDb.db (previously output.mdb in LRE 2023 and earlier releases) to RawResults.zip only if it is smaller in size than the RawResults.zip file size specified. Always exclude output.mdb/SqliteDb.db.zip from RawResults.zip. Collator process always excludes output.mdb (or SqliteDb.db.zip in LRE 2023 R1 and later) from RawResults.zip.
   Timeout | Collate Timeout (Min). The maximum amount of time, in minutes, the collate process should continue running without progress.

Back to top

See also:

- LoadRunner Enterprise basics
- View the dashboard
- Create domains and projects
- Manage projects

https://admhelp.microfocus.com LoadRunner Enterprise 8942
Tips to improve your search results... LoadRunner Enterprise Help Center LoadRunner Enterprise Help LR Enterprise Help 2023-2023 R1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: