To run Vusers from the LoadRunner Controller, you need an appropriate LoadRunner license and license bundle. To view the available license bundles, see the appropriate License Bundles PDF in the HPLN LoadRunner File Repository, in the LoadRunner and Performance Center Technical Documents section.
The Community Bundle
LoadRunner is delivered with a Community bundle replacing the Instant-on license. The Community bundle provides 50 Vusers with the following features:
- The bundle includes all protocols except for GUI (UFT) and COM/DCOM.
- You can run NUnit and JUnit tests with the Community bundle.
- You can use a maximum of 25 Noise Vusers with the Community bundle.
- You can use a maximum of 50 Noise and Web-HTTP/HTML Vusers combined.
- You can run two Vusers with Network Virtualization.
- The Community bundle does not include hidden protocols, which are no longer listed in the Create a New Script dialog box. Scripts created with such protocols in earlier versions of LoadRunner can still be replayed in the current version, but to conduct a load test with those scripts you need to purchase the appropriate bundle license.
- A multi-protocol Vuser will run only if licenses are available for all protocols in the Vuser script.
- If a multi-protocol script contains protocols from several bundles, you will need licenses for both bundles to run the Vuser script. The license for each Vuser will be subtracted from all relevant bundles. If at a certain point one of the bundle's license runs out, the Vuser will start to fail, even though there are still valid licenses for some of the other protocols.
If you purchased licenses for several different bundles (such as Web 2.0 and Oracle E-business) or several different license types (such as Permanent and VUD) which share common protocols and you want to run Vusers that belong to both bundles/types—the licenses will be consumed in the following order:
- License type:
- Temporary License
- Permanent and time-limited license
- VUD license
- Protocol amount: The bundle with the smaller number of protocols will be consumed before the bundle with a larger number of protocols.
- Capacity: The license with the larger capacity will be consumed before the license with the lower capacity.
VUD, Vuser-day licenses, are those issued with a limited capacity per day. For details on how to install VUD licenses, see License Utility.
- For the calculation of VUDs consumed in a VUD license, you can specify at what time each new day begins. LoadRunner determines the maximum number of Vusers that ran during the 24-hour period after the start time.
- To change the time at which a new day begins, click the VUDs will start at time link at the bottom of the LoadRunner License Utility.
- A VUD license may have an expiration date and therefore be time-limited.
- If you have both a non-VUD license (such as a time-limited or permanent license) and a VUD license for a particular Vuser protocol, LoadRunner will always use the non-VUD license before consuming the VUD license. Thus, if 500 Vusers were run on a particular day, and there is a regular license for 400 Vusers, then 100 VUDs will be deducted from the VUD license.
A Vuser is included in the VUD count as soon as the Vuser reaches the Initialization status in a scenario. Consumed VUDs are deducted from the available VUD capacity at the start of the following day. For example, suppose you purchased 100 VUDs for the Web 2.0 bundle:
At some point of time, T, on the date D, you start a scenario, with X Web -HTTP/HTML Vusers, where X is less than or equal to 100.
During the next 24 hours you can start and stop any number of scenarios, as long as the number of Vusers in each of scenarios is less than or equal to 100.
When point T on the date D + 1 arrives (exactly 24 hours after the first scenario launch), the Controller looks back at the previous 24-hours interval, locates the largest amount of Vusers that were ran simultaneously and subtracts it from 100. For example, if during the last 24 hours you ran three scenarios, with 20, 40 and 30 Vusers, the Controller will detect the use of 40 VUD’s and leave you with 60.
If a certain scenario is in progress during the time of the calculation (at the time T), it will be included in the calculation for both days on which it ran. For example, if you launch a scenario with 40 Vusers and it runs for 30 hours, then you will have used 40 VUDs for two days, and at the time T on the date D + 2 you will be left with 100 - 40 – 40 = 20 VUDs.
If a scenario runs for more than one day, the maximum VUD usage is calculated and deducted based on the day that the scenario began.