When running a load test, you may notice that the transaction number of times the transaction was repeated was not as defined in the BDL script: Script: .. dcluser user VUser transactions TInit : begin; TMain1 : 2; //TMain1 is defined to be repeated 2 times TAgain : 1; .. During load test, was noticed to have repeated 9 times: The script defined value is only effective for Queuing workload model. For the other workload models, the transactions are required to loop so as to meet the defined simulation time, or when the test simulation is stopped. The scripted value will define the pattern that is followed, i.e. in the above scenario TMain will execute 2 times, and then TAgain will execute once, before the pattern is repeated again. To ensure that the transaction have a fixed repetition regardless of the Workload model chosen, a loop can be defined within the transaction and when the repetition count is reached, perform a "return 2" or "halt" to stop the user simulation Note: - "return 2" and "halt" functions will terminate the user simulation immediately without executing the end transaction. - Looping within a transaction will not increment the transaction counter in monitor, and test results.
↧