Keeping threads spinning mitigates a ton of problems that simply parking threads willy nilly causes.
It automatically makes the UI more responsive as threads will constantly be "searching" for the lowest utilized core to execute on, which is excellent for making sure that when n-1 cores are at 100% load your system doesn't lock up if/when your other important threads are stuck on the same core as something else that is taking tons of core processor time.
That's one of the main reasons why Windows 7 is different than Windows 10 in this aspect, as gaatjes shows in the previous post.
Windows 7 is a 100% performance first philosophy in terms of core parking vs core spinning.
Windows 10 is more tilted towards trying to get as much of the silicon dark as possible (as it is targeted at mobile, laptop, and tablet use-cases) and in general doesn't spin threads around cores as much as Windows 7 does while also trying to save some power by "double-pumping" active cores instead of trying to get 100% utilization on physical cores first (which Windows 7 does for latency and performance reasons).
Note, this (Windows 10) behavior has plagued gamers ever since windows 10 was released to beta testing but has improved somewhat over time.
It was so bad at the beginning that your mouse couldn't even poll at 1000 hz properly due to all the forced power saving "design features" of windows 10. It also effected the audio output horribly in the beginning for the same reasons.
It automatically makes the UI more responsive as threads will constantly be "searching" for the lowest utilized core to execute on, which is excellent for making sure that when n-1 cores are at 100% load your system doesn't lock up if/when your other important threads are stuck on the same core as something else that is taking tons of core processor time.
That's one of the main reasons why Windows 7 is different than Windows 10 in this aspect, as gaatjes shows in the previous post.
Windows 7 is a 100% performance first philosophy in terms of core parking vs core spinning.
Windows 10 is more tilted towards trying to get as much of the silicon dark as possible (as it is targeted at mobile, laptop, and tablet use-cases) and in general doesn't spin threads around cores as much as Windows 7 does while also trying to save some power by "double-pumping" active cores instead of trying to get 100% utilization on physical cores first (which Windows 7 does for latency and performance reasons).
Note, this (Windows 10) behavior has plagued gamers ever since windows 10 was released to beta testing but has improved somewhat over time.
It was so bad at the beginning that your mouse couldn't even poll at 1000 hz properly due to all the forced power saving "design features" of windows 10. It also effected the audio output horribly in the beginning for the same reasons.
Facebook
Twitter