Forum Discussion
Kai_Wilke
Jan 31, 2018MVP
Hi Shipszky,
beside of the build-in iRule option (click me), you could also measure the time needed to execute certain commands / code blocks by counting the cycles needed with a very simple syntax...
Store the start time
set start_time [clock clicks]
This is the command we would like to check.
set aes_key [AES::key 256]
Store the stop time
set start_time [clock clicks]
Log the calculated time taken
log local0.debug "Time Taken: [expr { $stop_time - $start_time }]"
The output of this simple ample is not as granular as the build-in timing option, but on the other hand much easier to use.
Note: Personally, I use the iRule below to develop my iRules and test the performance of individual commands and code blocks. The iRule has also a build in function to statisticaly calculate the time taken over multiple request...
Cheers, Kai