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.
As per MSDN: The Stopwatch measures elapsed time by counting timer ticks in the underlying timer mechanism. If the installed hardware and operating system support a high-resolution performance counter, then the Stopwatch class uses that counter to measure elapsed time. Otherwise, the Stopwatch class uses the system timer to measure elapsed time. Use the Frequency … Read more
I would suggest using TimeUnit. You can use it like this: long minutes = TimeUnit.MILLISECONDS.toMinutes(millis); long seconds = TimeUnit.MILLISECONDS.toSeconds(millis);
No, you don’t need to stop it. Stop() just stops tracking elapsed time. It does not free up any resources.
You’ll find one in http://commons.apache.org/lang/ It’s called org.apache.commons.lang.time.StopWatch But it roughly does the same as yours. If you’re in for more precision, use System.nanoTime() See also this question here: Time measuring overhead in Java
Stopwatch is designed for this purpose and is one of the best ways to measure time execution in .NET. var watch = System.Diagnostics.Stopwatch.StartNew(); // the code that you want to measure comes here watch.Stop(); var elapsedMs = watch.ElapsedMilliseconds; Do not use DateTime to measure time execution in .NET. UPDATE: As pointed out by @series0ne in … Read more