Rendezvous: rendezvous point
===== >> loadrunner virtual users, the concurrent concurrent \ while simultaneous distinction:
concurrent concurrent: refers to the virtual user virtual scene involved in running concurrently,
simultaneous simultaneously: and rendezvous point closer to the assembly point, referring to the virtual user to perform a task with the same time.
Example:
Scenes:
10 athletes to participate in long-distance race, starting at the same time starting point, they are running side by side; N after running laps, because the efficiency of their formation side by side into a back and forth. It can be said at this time a track can supply them before and after the run (run), and that at this time the rest of the nine runway is idle.
In order to fully utilize resources runway, runway starting point can be set to a collection point, when all athletes lapped at the starting point after the set, and then start again at the same time.
Athletes can be seen as a virtual user, the runway can be seen as system resources. Set points can simulate more realistic set of concurrent requests, thereby increasing the load on the test system.
Example:
as follows:
1, open the login page
2, inserted into the collection point
3. Enter the user name and password, click the login button
4, the login page is loaded, the end of the recording
Note: Setting the set point system:
1, when the recording can be set as follows:
Mode 2, when the familiar script-action, can find the corresponding script and insert function yourself: lr_rendezvous () function Rendezvous
-------------------------------------------------------------------------------------------------------------------------------
Controller controller provided Rendezvous Method:
In the Virtual User Generator script does not reflect the role played back in the set point.
Rendezvous is in order to work in a multi-user concurrent operation time. It is necessary to put the script into the Controller for further settings.
1. Open the Controller (Controller), import recorded script.
2, the menu bar Scenario ---> Rendezvous Open rendezvous settings interface
Vusers list box there are 10 collection points (1 to 10), the same number here and we set the number of virtual users. (You can also click to select a collection point, click "Disable VUser" button, so that it does not participate in the rendezvous point.)
Bomb box meanings:
Release when: When all of the virtual user reaches the set point into the x% release, i.e. only if the specified percentage of the virtual user reaches the set point, and releases the virtual user. Note: This option would interfere with the planned scenario. If you select this option, the scenario will not run according to plan.
Release when: the release when all virtual users running the collection points to reach x%, that is, only when the scene specified percentage of virtual users running upon arrival at the rendezvous point release virtual users. There -------------- virtual users not running the state? If, set to 1 minute to start a user, of course, exist because the user did not start, so I can not participate in the rendezvous.
Release when: x virtual released when the user arrives at the rendezvous point, that is, only when the specified number of virtual user arrives at the rendezvous point, before the release of virtual users. When the number of virtual users I measure the set point percentage is not very good, of course, you can set a specific number of users.
Timeout between Vusers (time-out between the virtual user) a timeout value input box. If you set up a collection of 10 concurrent users, the result of nine users have assembled in place, left a virtual users to wait for that and so do not come. That it can not wait forever. Set time, if not for 30 seconds, then regardless of it. ------------- long default timeout is 30 seconds, we can be adjusted according to the specific application of the test