On Tue, 2 Aug 2011 00:19:32 +0100, Charles Forsyth wrote:
ron, by contrast, was timing a particular short interaction, which might be repeated a great many times (and thus mount up), where non-trivial overhead of taking the measurement could easily hide significant differences between two implementations, hence the use of a timer provided directly by hardware.
With the course timing I am currently doing this should be OK, but if I end up doing finer scale testing it will probably be in the us range. So, I would like to figure out how to do low overhead measurements if it will not take a lot of my time to get it working.
