Page History
...
Mapping VUs to dataset rows
By VU number
VU-bound and VU-Iteration-Bound both, by default, use the VU number to calculate which dataset row will be bound to a particular parameter. The advantage of this approach is that it is known ahead of time which record will be used for which VU and iteration.
...
| Note | ||
|---|---|---|
| ||
If the test has a unique data row constraint, then By VU number mapping will not work for tests that have changed VUs during the test run. |
Imagine a test with 2 test cases (TCA and TCB), and a particular dataset is only used for TCA. Since VUs are distributed between TCA and TCB in round-robin order, the VU numbers of VUs running TCA are not sequential. Therefore the dataset needs to be padded with dummy data for TCB that will never be used. So the datasets must have a sufficient number of records for VUs in all scripts, including those that do not use it.
...
On-Demand
...
This will assign rows to parameters on a first-come basis in run-time on-demand only for VUs that actually require data binding. So in the example above, the dataset doesn't need to be padded with dummy data.However, since Since the rows are assigned on-demand, there is no way to tell ahead of time which row will be assigned to which parameter. This method supports changed VUs during the test run.
| Note | ||
|---|---|---|
| ||
To use this method in a distributed test where VUs from different load agents share this dataset, agent-designated data is required. |
When the last record is reached
...
Overview
Content Tools