The order in which transactions are executed during a load test are defined within the dclUser section of a BDL script. In the above example, this means that TmyTrans1 will execute the three times during replay, TmyTrans2 transaction will execute four times and TmyTrans3 five times. Each transaction in the order in which it has been defined. By selecting the 'Choose transactions randomly' option - SILK PERFORMER | SETTINGS | ACTIVE PROFILE | SIMULATION (REPLAY) | SIMULATION, the transactions will not run in a sequential order, but randomly, e.g: The image above shows the first transaction to execute was TmyTrans3, as opposed to TmyTrans1, with the second iteration of TmyTrans3 being the third transaction executed during Replay. By selecting the 'Choose transactions randomly' option, the numbers of times a transaction iterates is not affected. Transactions will still iterate the set times which have been defined within the dcluser section. There are two ways to determine this is true: a) Refer to the replay TrueLog file and review the iterated transactions b) Implement functionality within the BDL script, which will count the number of times the transaction iterates, i.e: transaction TmyTrans1 var i : number; begin writeln(" "); sBuf := GetTransactionName(); WebPageUrl("http://demo.borland.com"); writeln("The transaction name is " + sBuf + " count " + i); i := i + 1; end TmyTrans1; This will generate an output file (.wrt file - ensure the 'Virtual User Output Files' option is selected - SILK PERFORMER | SETTINGS | ACTIVE PROFILE | RESULTS | GENERAL is selected), which will provide the number of times a transaction has iterated. It is important to note the count begins at zero rather than one. So the output of the transaction above would be: The transaction name is TmyTrans1 count 0 The transaction name is TmyTrans1 count 1 The transaction name is TmyTrans1 count 2
↧