Home/ Questions/Q 777895
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T19:40:53+00:00

I need an accurate timer, and DateTime.Now seems not accurate enough. From the descriptions

  • 0

I need an accurate timer, and DateTime.Now seems not accurate enough. From the descriptions I read, System.Diagnostics.Stopwatch seems to be exactly what I want.

But I have a phobia. I’m nervous about using anything from System.Diagnostics in actual production code. (I use it extensively for debugging with Asserts and PrintLns etc, but never yet for production stuff.) I’m not merely trying to use a timer to benchmark my functions – my app needs an actual timer. I’ve read on another forum that System.Diagnostics.StopWatch is only for benchmarking, and shouldn’t be used in retail code, though there was no reason given. Is this correct, or am I (and whoever posted that advice) being too closed minded about System.Diagnostics? ie, is it ok to use System.Diagnostics.Stopwatch in production code?
Thanks
Adrian

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Under the hood, pretty much all Stopwatch does is wrap QueryPerformanceCounter. As I understand it, Stopwatch is there to provide access to the high-resolution timer – if you need this resolution in production code I don’t see anything wrong with using it.

    • 0