Windows Scheduler description

"The Windows scheduler is pretty basic. Spinning threads get all the cpu they can chew; being in a foreground Window gives a pretty high bias, but otherwise things seem to be evenly spread. AricStewart did a test program which showed how SetThreadPriority biases things; it tends to be that only priorities -2 through 2, and 15, have any meaning. Further, if threads yield, then only the top priority threads get any time. If all threads 'work', then there is a stair step effect where high priority threads get 'more', but don't necessarily get it all."

• - Jeremy White