This article, which is part of a series on “High-performance programming techniques on Linux and Windows” at IBM's developerWorks website, looks at two behaviors of the scheduler. The first is the reaction to adding more choices to the scheduler's switching decision. The second demonstrates fairness, by performing a uniform workload in multiple threads. Source code is provided so you can experiment on your own. Part 1 looked at bare context switch times by using the best primitives on both Windows and Linux. According to those results, context switch time under Windows takes only half as long as under Linux.