Re: How do you set time-slicing for Windows XP

Tech-Archive recommends: Fix windows errors by optimizing your registry



"Jochen Kalmbach [MVP]" <nospam-Jochen.Kalmbach@xxxxxxxxx> wrote in message news:OIkh96X#IHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
Hi Pavel!

Certainly, time slice unit is based on resolution of the periodic timer tick
( it can not be less than the tick period?)
but these are two different things.

???

See comment in the documentation of "timeBeginPeriod":

<quote>
This function affects a global Windows setting. Windows uses the lowest value (that is, highest resolution) requested by any process. Setting a higher resolution can improve the accuracy of time-out intervals in wait functions. However, it can also reduce overall system performance, because the thread scheduler switches tasks more often. High resolutions can also prevent the CPU power management system from entering power-saving modes. Setting a higher resolution does not improve the accuracy of the high-resolution performance counter.
</quote>

So setting "1" means, that the scheduler will be called much more than normal.

Agreed.

This indicates that the reduction of the thread-quantum is done inside *this* tick-counter. Which leads to the effect, that the thread-switch-count will increase dramaticaly.

Still not sure that the thread quantum would become shorter if the timer ticks more often.

--PA


.



Relevant Pages

  • Re: How do you set time-slicing for Windows XP
    ... (it can not be less than the tick period?) ... However, it can also reduce overall system performance, because the thread scheduler switches tasks more often. ... Setting a higher resolution does not improve the accuracy of the high-resolution performance counter. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: How do I get an accurate time in CF?
    ... higher resolution. ... I'm reading from a connection and ... > DateTime.Now.Ticks is supposed to be the tick count. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: now.ticks does not work
    ... > If the timer happend to tick just between the first and 2nd call to 'Now', ... > The "^" indicate the points where the measurements take place. ... > timer with a higher resolution. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: now.ticks does not work
    ... As the resolution is 0.01 seconds, ... It returns 0.02 after the 2nd tick. ... timer with a higher resolution. ...
    (microsoft.public.dotnet.languages.vb)