[wpkg-users] [Bug 233] Command invokations cause unneccessary delays

[Rainer Meier]

Hi Stefan,

On 02.08.2011 09:46, Stefan Pendl wrote:
> The minimum resolution of the regular Windows timer is about 16ms, so
> 10ms would never get reached.

I know the default clock resolution of Windows seems to be 15.6ms but 
applications can also request higher clock rates. I don't know all the details 
and cscript.exe is unlikely to set a more-precise clock. However in worst case 
my counter will just take ~156ms for the first 10 wait cycles using 10ms. Then 
it will continue with 100ms intervals and after 1 second it's back to 1s intervals.

Also don't worry about inaccurate time measuring. Every 10th interval the time 
really used by the script is synchronized with the clock.


btw. You can use Sysinternals ClockRes to get your current clock resolution.
<http://technet.microsoft.com/en-us/sysinternals/bb897568>

On my system currently it looks like:

ClockRes v2.0 - View the system clock resolution
Copyright (C) 2009 Mark Russinovich
SysInternals - www.sysinternals.com

Maximum timer interval: 15.600 ms
Minimum timer interval: 0.500 ms
Current timer interval: 1.000 ms

Although I am not really sure what has set the current timer to 1ms resolution.

br,
Rainer