Platform dependency of thread management
-
A
Thread.Sleep(n)will pause the current thread for at least n milliseconds. But there are some caveats:Thread.Sleep(1)takes at least some 15 ms on "common" Windows 7/8/10 due to the "time slice" management of threads. In contrast, running the same code with mono on Linux, the sleep time may get close to 1 ms. I haven't found any information on Windows 10 IoT for that feature. Already this simple example shows that Threads are dealt with differently depending on the underlying platform. Where can I find more information on that feature? The main interest is differences between Windows 10 Pro and Windows 10 IoT, but also information beyond that is appreciated.Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
-
A
Thread.Sleep(n)will pause the current thread for at least n milliseconds. But there are some caveats:Thread.Sleep(1)takes at least some 15 ms on "common" Windows 7/8/10 due to the "time slice" management of threads. In contrast, running the same code with mono on Linux, the sleep time may get close to 1 ms. I haven't found any information on Windows 10 IoT for that feature. Already this simple example shows that Threads are dealt with differently depending on the underlying platform. Where can I find more information on that feature? The main interest is differences between Windows 10 Pro and Windows 10 IoT, but also information beyond that is appreciated.Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
Worse yet, Thread.Sleep doesn't even guarantee that the thread will actually give up its time slice. If there are no other threads ready to run at the same priority, your Thread is not suspended. T minimum time a Thread can "sleep" is dependent on the system timer and its resolution. The timer is dependent on hardware and O/S implementation. From the Sleep function[^] in the Win32 documentation:
Quote:
The system clock "ticks" at a constant rate. If dwMilliseconds is less than the resolution of the system clock, the thread may sleep for less than the specified length of time. If dwMilliseconds is greater than one tick but less than two, the wait can be anywhere between one and two ticks, and so on. To increase the accuracy of the sleep interval, call the timeGetDevCaps function to determine the supported minimum timer resolution and the timeBeginPeriod function to set the timer resolution to its minimum. Use caution when calling timeBeginPeriod, as frequent calls can significantly affect the system clock, system power usage, and the scheduler. If you call timeBeginPeriod, call it one time early in the application and be sure to call the timeEndPeriod function at the very end of the application.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak