Rendezvous Policy in LoadRunner

The complementary aspect of the rendezvous point involves the rendezvous policy. This policy allows us to configure how the controller releases Vusers from the rendezvous point. It can be based on either the arrival of the required number of Vusers or a predefined time duration.

Difference between Rendezvous Point and Rendezvous Policy

The Rendezvous Point and Rendezvous Policy are two distinct concepts within load testing frameworks like LoadRunner.

Rendezvous Point – Defined in Vugen

• The Rendezvous Point is a synchronization point in a load testing script where multiple virtual users (Vusers) converge to execute a task simultaneously.
• It ensures that Vusers wait until a specified number of Vusers have reached the designated point before proceeding with the test script execution.
• Its primary purpose is to simulate real-world scenarios where multiple users access a particular functionality or page concurrently, thereby creating a realistic load on the server.

Rendezvous Policy– Defined in Controller / LRE Scenario

• The Rendezvous Policy is a configuration setting used to determine the behavior of the Rendezvous Point during test execution.
• It defines how the controller manages the release of Vusers from the rendezvous point.
• The policy can be set based on conditions such as the arrival of a specific number of Vusers or a predetermined time limit.
• The Rendezvous Policy helps prevent scenarios where all Vusers are indefinitely delayed due to a single Vuser not reaching the rendezvous point, thereby ensuring the smooth execution of the test.

In summary, while the Rendezvous Point serves as a synchronization mechanism for Vusers, the Rendezvous Policy dictates the rules governing the release of Vusers from the rendezvous point, thereby optimizing test execution and maintaining test integrity.

Importance of Rendezvous Policy:

Suppose you have integrated a rendezvous point into your test script, where all Vusers are expected to wait until the final one arrives, as per the standard definition. However, in certain instances, if the last Vuser encounters issues and fails to reach the rendezvous point, it can result in all Vusers pausing for an extended period, awaiting the stuck Vuser. This scenario undermines the test’s intended purpose. To mitigate such occurrences, a Rendezvous policy is employed. This policy ensures the test continues to run smoothly by adhering to specified conditions.

How to add a Rendezvous policy in a LoadRunner scenario:

Rendezvous points are exclusively functional within group mode when utilizing the manual scenario and are disabled for goal-oriented scenarios. Upon adding a Vuser group or script to the scenario, LoadRunner scans the incorporated scripts for rendezvous points and aggregates them into a centralized list. In the controller interface, you are required to configure Rendezvous policy. See below steps on how to do so.

Select Scenario (Design) > Rendezvous to view this list.

Click on Rendezvous

Click on Policy

Policies – A brief of what different policy options mean and which one to select:

• Release when XXX % of all Vusers arrive at the rendezvous: Suppose there are 100 Vusers in total, with 20 in a downstate, 20 in a ready state, and 60 actively running. If the aim is to release 40% (equivalent to 40 Vusers) after a 30-second wait, the value input in the designated box would be 40.
• Release when XXX % of all running Vusers arrive at the rendezvous: Consider a scenario where there are 100 Vusers in total, comprising 20 in a downstate, 20 in a ready state, and 60 actively running. Suppose the objective is to release 40% of the running Vusers (equivalent to 24 Vusers) after a 30-second wait; therefore, the value input in the designated box would be 24.
• Release when XXX Vusers arrive at the rendezvous: For instance, considering a scenario with 100 Vusers, where 20 are in a downstate, 20 are in a ready state, and 60 are actively running. If the goal is to release 60 Vusers after waiting for them for 30 seconds, then the value to input in the designated box would be 60.
• Timeout between Vusers YY Sec.: This refers to the duration that the controller waits before releasing Vusers from a rendezvous point.

Important points to keep in mind:

• Rendezvous points are only applicable for group mode scenarios.
• Do not insert a Rendezvous point inside a transaction.