LoadRunner controller: Aggregation point policy

A collection point can only be useful if it is run concurrently by multiple users.

Scenario---> Rendezvous Open the collection point settings interface as shown in:

We can see that there are two users in the vusers list box, which is the number of virtual users we set up and can be "Enable vuser" to determine whether a user participates in the meeting point;

In the Rendezvous list box you can see our collection point, where in the script I only set a collection point login, again, we can use "Disable Rendezvous" to make the collection point does not work.

Below we click on the policy below the Rendezvous list box ... To open the collection Point Policy Settings window, such as:

three different strategies :

1) When x% in all virtual users arrives at the collection point, the virtual user is freed only when the specified percentage of virtual users arrives at the collection point;

2) When x% of all running virtual users arrives at the meeting point, the virtual user is freed only when a running virtual user of the specified percentage in the scene arrives at the collection point.

3) When X virtual users arrive at the meeting point, the virtual user is freed only when the specified number of virtual users arrives at the collection point.

Finally there is a timeout between vusers (timeout between virtual users): If set up 10 users concurrency, the result 9 users have been assembled in place, there are 1 virtual users, in the set timeout of 30 seconds has not been set in place, regardless of it, 9 users to perform concurrency.

LoadRunner controller: Aggregation point policy