fixed time slices?

Hallo.

I've noticed that my XP computer seems to handle time-slices
difrent from what I think it used to.

The rule I remember it should be is like defined in the SDK:

| If a higher-priority thread becomes available to run, the system
| ceases to execute the lower-priority thread (without allowing it
| to finish using its time slice), and assigns a full time slice
| to the higher-priority thread.

But now, if I create a process/thread that does nothing but this:

repeat
for i := 0 to n do begin
setWaitableTimer(timer,...);
waitForSingleObjectEx(timer,...);
end;
write_time;
unitl false;


it turns out that the minimum wait intervall seems to be 15ms,
and other timer-inveralls are rounded up to something near a
multiple of that minimum wait intervall, even if I set a
high priority to that process and the system is otherwise idle.

The same thing happens using sleep().

What's going on here?

Gruss

Jan Bruns


.

Relevant Pages

  • Re: fixed time slices?
    ... | If a higher-priority thread becomes available to run, ... | to finish using its time slice), and assigns a full time slice ... if I create a process/thread that does nothing but this: ... it turns out that the minimum wait intervall seems to be 15ms, ...
    (microsoft.public.win32.programmer.kernel)
  • Re: fixed time slices?
    ... | If a higher-priority thread becomes available to run, ... | to finish using its time slice), and assigns a full time slice ... if I create a process/thread that does nothing but this: ... it turns out that the minimum wait intervall seems to be 15ms, ...
    (microsoft.public.win32.programmer.kernel)