Timer macro

Timer macro source code attached

Corrected error in comment - please use this one.

Another improvement; this one allows a string of user's choice - example:

timer "Overall elapsed time: ":
timer:
for i in range(len(x.a)):
x.a[i] = i

timer elapsed:
for i in range(len(x.a2)):
x.a2[i] = i
print "Elapsed = $

"

Output:
Elapsed time: 00:00:00.6208928
elapsed = 00:00:00.6309072
Overall elapsed time: 00:00:02.2832832

Sorry - forgot to update help string too.

New version takes optional argument for number of times to loop over code. It does loop unrolling to minimize impact of loop code on timer (default is to repeat code 8 times within loop body). The loop code is very fast (doesn't use iterator, its just a simple loop). This macro is the most accurate way to time things.

New syntax:

timer [nLoops [, unroll]] [, "Message: "] [, elapsedTimeVar]

Example:

timer 1000002:
f = fact(20)

generates this code:
_startTime1_ = System.DateTime.get_Now()
_loopCounter1_ = 0
while (_loopCounter1_ < 125000):
_loopCounter1_ = (_loopCounter1_ + 1)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
f = UntitledModule.fact(20)
_elapsedTime1_ = System.DateTime.op_Subtraction(System.DateTime.get_Now(), _startTime1_)
System.Console.Write('Elapsed time for 1000003 executions: ')
System.Console.WriteLine(_elapsedTime1_)

Printed message in code above should read "1000002 executions" not "1000003 executions".

Latest attachment properly inherits from AbstractAstMacro

Completely rewritten.
Usage: timeIt [label] [, iterations] [, elapsed]

Example with all arguments.
NOTE: The label argument is ignored if you pass the last argument.

elapsed as timespan
timeIt "Loop", 10, elapsed:
index = 0
while (index < 50000):
++index

I changed the regex in your test fixture to \d*?:\d*?:\d*?\.?\d*
instead of \d*?:\d*?:\d*?\.\d*
(put a question mark after last period)
Because time was being printed like 00:00:00 instead of 00:00:00.00

Doug,

I'm afraid I can't vouch for this macro anymore - it was rewritten in Boo, and I think (from a short code inspection) that it will not be accurate anymore. In the C# version, I went to a lot of trouble to do loop unrolling so that the overhead of looping would not interfere with the results. In the Boo version, there is no loop unrolling, and also the elapsed time seems to be incremetally calculated within the loop, which due to the low system clock resolution will totally throw things off.

• Bill