3 ms·
I have had a quick look through here [1] and most of the answers involve timing precision of two significant digits. By that metric, PowerShell's 2.4ms clocks i
by taspeotis 10y ago
I have had a quick look through here [1] and most of the answers involve timing precision of two significant digits. By that metric, PowerShell's 2.4ms clocks in at 0.00 seconds. Which means cmd.exe (at a precision of two significant digits) can't beat it.
[1] http://stackoverflow.com/questions/673523/how-to-measure-execution-time-of-command-in-windows-command-line http://stackoverflow.com/questions/673523/how-to-measure-exe...
- Arnavion 10y ago"2.4" or "0.0024" or "24000" all have two significant digits. Leading and trailing zeros don't count as significant digits.
- taspeotis 10y agoMy mistake, you are right [1]. Thanks for the correction. [1] https://en.m.wikipedia.org/wiki/Significant_figures https://en.m.wikipedia.org/wiki/Significant_figures