Windows 10 v1909 CPU Scheduling changes

[Coldblackice]

Jeremy, any thought or comment on this new Windows 10 "feature" coming in this latest version, particularly how Process Lasso will A.) compare with it in terms of ability/functionality, and B.) if and how they'll get along without clashing, like will one have to be disabled manually, will PL need time to adapt, etc.?

Windows 10 version 1909 has a new CPU rotation capability. It'll balance the work across the OS' so-called "favored cores," which is designed to improve system performance and reliability. Microsoft also initiated "additional debugging capabilities for newer Intel processors" in this OS release

https://redmondmag.com/articles/2019/11/12/windows-10-version-1909-released.aspx

For the record, I ask this only in a sense of curiosity in wanting to know more about scheduling on a more technical level, but having full trust and expectation that PL could and surely will do this better, particularly given Microsoft's track record with Windows 10. I'm wincing in anticipation of the inevitable problems that will come about from this "feature", like nearly every other Windows 10 update in the years since its release.

We really need a "Windows 11", though fat chance of that happening. W10 just keeps getting worse/buggier/bloated/offtrack. What did Microsoft expect would happen when they laid off a huge part of their QA testing teams 

[Jeremy Collake]

There really isn't any conflict. This change is just further refinement to the Windows CPU scheduler to handle today's multi-core chips that have some cores that can be marginally faster than others on the same chip. Nobody predicted that years ago.

This just improves how it shuffles the threads to prevent overloading a single core and keep the thermal load distributed among the available fastest cores.

It isn't a huge deal. Like innumerable other low-level scheduler optimizations and features, this change doesn't impact Process Lasso.

You can consider it micro vs macro optimization. Process Lasso operates at the macro process/app level, while the OS scheduler acts on software threads (a process can have any number of threads).

While Process Lasso allows humans to apply CPU afifnities and other settings that might change end scheduler behavior, it is presumed the human is acting with some intelligence, or has a high-level need to change the behavior.

Similarly, ProBalance's priority class adjustments are not impacted by this or other scheduler change.