Number of iterations in LR set

When parameterized, what should be the parameterization of the resources that can only be used once in a stress test ? It means that these resources cannot be used once.

--When parameterized, select Unique,update value on the Select Next row to choose each occurence, 1. Iterations are not necessarily associated with the number of virtual users　　Iteration is like this: iterate 1 times   Iterate 2 times   Iterate 3 times user 1     X1           X2       &N Bsp　　    X3 users 2     Y1           X2             Y3　　The X1-3 y1-3 is the parameter, the parameter rule is the second floor said so two users are based on your rump up, such as 5 seconds on two users, then the user 1 and 2 in 5 seconds to load in, do not know to say clearly not.　The second problem is simple, can only be used once the parameters, first of all to ensure that your parameters enough, in addition to the rule selection, note that the choice of unique iterations is only the number of iterations you set the action to iterate, and the number of users can be understood as an iteration of the entire recording process (only different users) and the increase in concurrency can be achieved by increasing the number of users can also set the collection point to increase the concurrency of an operation if a script, set the maximum concurrency of 10, 2 concurrent users per 5 seconds, and the action set to iterate 10 times: When the start to 2 seconds, the load of 2 users,　　The 2 users began to run, and both ran 10 times, regardless of whether the 2 users run 10 is the end, when the next 2 two seconds to arrive, that is, start to 4th seconds when the load of 2 users, 2 run 10 times, and then load to 10 concurrent users, and then when each user finished running 10 times the end.　　So the middle maximum concurrency is 10, but not necessarily can reach 10, because in the last few load, the previous may have been running the end, so if you want to really reach the maximum concurrency of 10 must set the collection point to complete　　However, it is not necessary to set the collection point to implement a state that is in running at the same time with 10 users. Setting up the duration is also possible.　　But that will not only run 10 times per user.　　If you want to implement a user iteration 10 times, and want to running at the same time as 10 users, you should set the collection point.　　The idea of iterative (iterate) design, or what we call incremental (Incremental) design, is similar to the one that XP advocates for evolutionary. Note: 1, parameter type: When I created the parameter, I chose the parameter type as file. There are 9 kinds of parameter types, so let's take a brief look at all the parameter types and meanings.　　1.1,   datetime: You can substitute a datetime type where you want to enter a date/time. Its property settings are also simple, select a format.　　Of course, you can also customize the format. 1.2,   Group Name: rarely used. In practice, LoadRunner uses the VUser Group that the virtual user resides in instead.　　However, when running in Vugen, the Group name will be none.　　1.3.   Load Generator Name: In practice, LoadRunner   uses the loadgenerator   machine name that the virtual user is in instead.　　1.4,   Iteration number: In actual operation, LoadRunner uses the test script to replace the current loop. 1.5.   Random number: randomly. Very simple.　　You can set the range that produces the random number in the property settings. 1.6,   unique number: unique.　　You can set the size of the first number and the number of increments in the property settings. Note: Use this parameter type to be aware of the maximum number that can be accepted. For example, the maximum number that a text box can accept is 99. When the parameter type is used, the first number is set to 1 and the increment is 1, but when 100 virtual users run concurrently, the 100th virtual user enters 100, so the script runs with an error. This increment means that each user takes the increment of the first value, and the difference between the two loops adjacent to each user is 1. Example: If the starting number is 1, increment to 5, then the first user first cycle to the value of 1, the second cycle to the value of 2; the second user first loops with a value of 6, the second is 7, and so on.
　1.7,   VUser ID: Setup is relatively simple. In practice, LoadRunner uses the ID of the virtual user  , which is controlled by the controller, in place of the ID  .　　However, when running in Vugen, the VUser ID   will be –1.　　1.8,   file: You need to edit the file in the property settings, add content, you can also take data from the ready-made database 1.9,   user Defined Function: Extract data from user-developed DLL files. A script that contains the login, browse, and exit procedures is recorded with the HTTP protocol, and is recorded in the Action section, where the script can be repeated multiple times after the iteration has been set, but for processing logic, once the logon script is placed in the Init section, it cannot be run correctly.　　Find a time to try it today and find out that both of these errors may occur. 1, this is a low-level mistake I made. When I moved the logon script to the Init section, the Web_reg_find script in front of the browse operation after the logon script was also moved past, resulting in an error running through the init section of the script. Error tip: error-27259:pending WEB_REG_SAVE_PARAM/REG_FIND/CREATE_HTML_PARAM[_EX] Request (s) detected and reset at the end O f The Init section This error phenomenon is that there is no iterative error and the error message is clear.　　Just put the web_reg_find back in the correct position on the action section. 2, a single run is correct, but multiple iterations run error, error: Error-27985:there is no context for html-based functions. A previous function may not be used "mode=html" or downloaded only non-html page (s), or the context has been reset (e.g. , due to a gui-based function) This error can be common because simulate a new user on each iteration is set in the runtime settings's browse emulationCaused by.　　Because this setting causes a new user to be impersonated at each iteration, the new user fails to perform the init operation, which is the there is no context in the error message. One of the points of knowledge here is that in the iteration settings of the Rumtime settings, the number of iterations is only valid for the action part, and the Init and end parts run only once. If "Simulate a new user on each iteration" is set, the 2nd error above will appear.

Number of iterations in LR setting