Using MeasureStart and MeasureStop in your script will do this. (See online help for further details). This can be useful when you want to know the time it takes for a Vuser to execute a specific number of functions spread across transactions. The sample code below should illustrate how you can do this. NOTE : When using custom measures if MeasureStop is not present then the timer will not be created in the overview report. It is imperative that you do not run transactions randomly when using such timers as it may result in incorrect times being reported. You should also note that certain workloads may insert pauses between transactions and as such may affect the accuracy of these timers. Old KB# 19138
↧