Rendezvous Point and its Significance

Introduction :

Generally in the performance testing of any application if we want to stress by pumping load simultaneously on the particular transaction by making all the users or particular number of users load to the desired transaction as the simultaneously acting user load.

Rendezvous point in LoadRunner

• LoadRunner allows you to check your system’s response under specific load. To do this, you can use rendezvous points to cause multiple Vusers to perform tasks at exactly the same time, thereby creating intense user load on the server.
• During a scenario run, you can instruct multiple Vusers to perform tasks simultaneously by using rendezvous points. A rendezvous point creates intense user load on the server and enables LoadRunner to measure server performance under load
• Create the Vuser scripts, inserting the necessary rendezvous points.
• In loadrunner we will the handle this scenario by creation the lr_rendezvous("Rendezvous_point_name"); in the vuser generator script.
• Create a scenario in the controller or performance center.
• When you add a Vuser group to a scenario, LoadRunner scans the group’s associated script for the names of the rendezvous points and adds them to the list in the Rendezvous Information dialog box (Scenario> Rendezvous).

 If you create another Vuser group that runs the same script, the Controller adds the new Vusers to the rendezvous and updates the list.

Set the level of emulated user load.

You determine the exact level of load by selecting the rendezvous points that will take part in the scenario, and how many Vusers will participate in each rendezvous.

Set the attributes for the rendezvous (optional).

Run the scenario

.

Setting the Rendezvous Attributes

 You can set the following rendezvous attributes from the Rendezvous Information dialog box (Scenario> Rendezvous):

 Rendezvous Policy

 Enabling and Disabling of Rendezvous Points

Enabling and Disabling of Vusers.

• Uses: Rendezvous point mainly used to put the simultaneous users load on the particular transactions.
• It is also used to find the issue for the particular transaction where the users are hanging at same point of the application frequently.