Wednesday, August 05, 2009


(No, not the ones you get camping. This is a developer blog).

What’s a Tick? Depends who you ask. ‘Ticks’ are just how a given component chooses to measure time. For example,

DateTime.Now.Ticks = 100 ns ticks, i.e. 10,000,000 ticks/sec
Environment.TickCount = 1 ms ticks since process system start

These are just fine for timing webservices, round-trips to the database and even measuring the overall performance of your system from a use-case perspective (UI click to results back). But for really accurate timings you need to use system ticks, i.e. ticks of the high-resolution timer: System.Diagnostics.Stopwatch.GetTimestamp() [1]. This timer’s frequency (and hence resolution) depends on your system. On mine:

System.Diagnostics.Stopwatch.Frequency = 3,325,040,000 ticks/sec

…which I make to be 0.3ns ticks. So some 300x more accurate than DateTime.Now, and accurate enough to start measuring fine-grained performance costs, like boxing/unboxing vs generic lists.

Clearly it’s overkill to use that level of precision in many cases, but if you’re logging to system performance counters you must use those ‘kind of ticks’, because that’s what counter types like PerformanceCounterType.AverageTimer and PerformanceCounterType.CounterTimer require.

[1] Thankfully since .Net 2, we don’t have to use P/Invoke to access this functionality anymore. On one occasion I mistyped the interop signature (to return void), and created a web-app that ran fine as a debug build, but failed spectacularly when built for release. Took a while to track that one down...


Recep said...

"Environment.TickCount = 1 ms ticks since process start"

Isn't that supposed to be system start?

piers7 said...

Absolutely. My bad. I wonder where I got that idea from.

Anonymous said...

Holy crap, how is your Stopwatch.Frequency so high?! Mine is only 2597705, which translates to about 385 ns per tick. I'm on an i7 920 machine, shouldn't it be faster?

piers7 said...

Good question. That's my work PC, a Core 2 Duo @ 3.33 GHz

My 2.2 GHz Turion X2 laptop at home only gets 14,288,396, and my HP mini netbook a mere 1,558,642.

All these are idle timings, however I didn't think that the stopwatch frequency was affected by CPU clock-rate shifting technologies. Otherwise a stopwatch timing that spanned over a idle/busy period would report completely the wrong duration.

So basically: I have no idea. Sure you didn't just drop a digit?

Popular Posts