Distribute Vusers among Vuser groups

This task describes how to distribute Vusers in a performance test among the Vuser groups. You distribute Vusers according to the Vuser distribution method you selected for the workload.

You can distribute the Vusers by number, by percentage (manually), by percentage using the relative distribution method, or by goal.

Note: In workloads with group schedules, you can distribute Vusers by number only.

Vuser distribution methods

You select a Vuser distribution method for a performance test from the Workload Types dialog box. The type of workload you choose determines the type of schedule by which the test will run, and how the Vusers will be distributed at runtime.

Note: If you change the workload, Scheduler settings are lost.

To select a workload type:

  1. Open the Workload Types dialog box:

    • In the Performance Test Designer window, click Groups & Workload. Next to the Workload type box, click Select Workload Type.

    • From the LoadRunner Enterprise navigation toolbar, click and select Create New Performance Test.

  2. Select a workload type:

    UI Elements

    Description

    Basic schedule, by test. Select this workload type to configure all the Vuser groups to run together on the same test schedule, in the basic run mode.

    Vusers can be distributed:

    • By number. The Vusers are distributed by number.

    • By percentage. The Vusers are distributed by percentage.

    Basic schedule by group. Select this workload type to configure each Vuser group to run on its own test schedule, in the basic run mode.

    In group schedules, Vusers are always distributed by number.

    Real-world schedule, by test. Select this workload type to configure all the Vuser groups to run together on the same test schedule, in the real-world run mode.

    Vusers can be distributed:

    • By number. The Vusers are distributed by number.

    • By percentage. The Vusers are distributed by percentage.

    Real-world schedule, by group. Select this workload type to configure each Vuser group to run on its own test schedule, in the real-world run mode.

    In group schedules, Vusers are always distributed by number.

    Goal-Oriented Schedule. Select this workload type to define the goals you want your test to achieve. You can specify the number of Vusers to run simultaneously, or the number of Hits or Transactions Per Second. LoadRunner Enterprise automatically builds a schedule based on the selected goals. For details, see Distribute Vusers by goal.

    Note: When you select this workload type, the Goal Definition pane is displayed in the Groups and Workload tab (Performance Test Designer) page (the Global Scheduler is hidden).

Back to top

Distribute Vusers by number

When distributing Vusers by number, choose one of the following schedules:

Note: This procedure assumes that you selected By number when you selected the workload for the test. For user interface details, see Vuser distribution methods.

  • Basic schedule: In the Performance Test Designer window, in the Groups grid, select a group, and in the Vusers column, enter the number of Vusers to allocate to that group.

  • Real-world schedule: You define the number of Vusers when you define the test schedule. For details, see Define a schedule for the test.

For both run modes, the total number of the Vusers assigned to all the Vuser Groups is displayed in the Groups pane toolbar.

Back to top

Distribute Vusers by percentage

This task describes how to distribute Vusers by percentage.

Note: This procedure assumes that you selected By percentage when you selected the workload for the test. For user interface details, see Vuser distribution methods.

  1. In the Performance Test Designer window, in the Groups grid, in the Vusers-100% column for each group, enter the percentage of the total number of Vusers to allocate to the group.

    Note: The total of all the groups' percentages must be exactly 100% for the test to be valid.

  2. Allocate a total number of Vusers to run in the test:

    • Basic mode: In the Groups pane, enter the number of Vusers in the Total Vusers box.

    • Real-world mode: You define the number of Vusers when you define the test schedule. For details, see Define a schedule for the test.

Back to top

Distribute Vusers by percentage using relative distribution

In the Performance Test Designer window, in the Groups grid, click the Relative Distribution button to define a ratio by which to distribute the Vusers from each group. For user interface details, see Relative Distribution in Performance Test Designer > Groups & Workload.

Back to top

Distribute Vusers by goal

In a goal-oriented schedule, you define the goals you want your test to achieve, and LoadRunner Enterprise automatically builds a schedule for you based on these goals.

Note: You cannot run Network Virtualization while using a Goal-Oriented schedule.

  1. Prerequisites

    Before setting up the test, decide which goal you want the test to reach. For details on types of test goals, see Goal types for goal-oriented schedule.

  2. Assign each script a percentage of the total test target

    In the Performance Test Designer window, in the Groups grid, enter the percentage of the total goal you want each script to reach during the test in the % of Target column for each group.

    Note: The total of all the groups' percentages must be exactly 100% for the test to be valid.

  3. Define a goal for the test

    1. In the Goal Definition For pane, click the adjacent drop-down arrow, and select a goal type.

    2. Configure the goal settings:

      UI Element Description
      Reach Goal <value> <goal type>

      Enter the desired goal (number of Vusers to run, Hits Per Second, or Transactions Per Second).

      For the Transactions per Second goal type, you also specify a transaction name.

      # of Vusers

      Enter a minimum-maximum range of Vusers for the scheduler to run.

      Note: Available for Hits/Transactions Per Second only.

      Duration Run For <duration>

      The amount of time (in days, hours, minutes, and seconds) to run the test.

      Goal Missed

      The action to be taken if the target cannot be reached.

      • Stop test and save results.

      • Continue test without reaching goal.

      Schedule Preview A graphical representation of the goal and load behavior defined for the test.
  4. Configure test options (optional)

    By default, LoadRunner Enterprise runs the test using the think time recorded in the script (this might require running additional Vusers in your test in order to reach your target). If necessary, you can disable this setting for the test. For details, see Configure test options.

Back to top

Goal types for goal-oriented schedule

You can select the following types of goals for a goal-oriented schedule:

Goal Type Description
Vusers Tests if your application can run a specified number of Vusers simultaneously. Running this type of goal-oriented schedule is similar to manually distributing Vusers by number.
Hits per Second/Transactions per Second

These goals test the strength of your server.

When you define one of these goal types, the Controller divides the target defined by the minimum number of Vusers specified, and determines the target number of hits/transactions per second that each Vuser should reach.

After running each batch of Vusers, LoadRunner Enterprise evaluates whether the target for the batch was achieved. If the batch target was not reached, LoadRunner Enterprise recalculates the target number of hits, transactions, or pages per Vuser, and readjusts the number of Vusers for the next batch to be able to achieve the defined goal. By default, a new batch of Vusers is released every two minutes.

If the goal has not been reached after the Controller has launched the maximum number of Vusers, LoadRunner Enterprise attempts to reach the defined target once more by recalculating the target number of hits or transactions, and running the maximum number of Vusers simultaneously.

A Hits/Transactions per Second goal-oriented scenario is assigned a Failed status if:

  • The Controller has twice attempted to reach the goal using the maximum number of Vusers specified, and the goal could not be reached.
  • No hits/transactions per second were registered after the first batch of Vusers was run.
  • The number of hits/transactions per second did not increase after the Controller ran a certain number of Vuser batches.
  • All the Vusers that ran failed.
  • There were no available load generators for the type of Vusers you attempted to run.

Back to top

See also: