Wednesday, October 6th 2021
AMD Processors Lose 15% Gaming Performance with Windows 11, L3 Cache Latency Tripled
Apparently, AMD processors officially compatible with Windows 11, exhibit a three-times increase in L3 cache latency with the new operating system. The new operating system is also found to break the "preferred cores" system on AMD processors (UEFI CPPC2), in which the two "best" CPU cores, which can sustain the highest boost frequencies, are highlighted to the operating system, so most of the light-threaded traffic could be sent to them.
AMD and Microsoft jointly made this discovery, and listed out potential impact on application performance. The increased L3 cache latency affects performance of applications sensitive to memory performance. They also warn of a 10-15% loss in gaming performance. On the other hand, a dysfunctional "preferred cores" system would mean reduced performance in light-threaded tasks as the OS is unaware which are the processor's two best cores. Thankfully, both issues can be fixed via software updates, and AMD is working with Microsoft to push fixes for both issues through Windows Update, in an update rollout scheduled within October 2021.
Source:
AMD
AMD and Microsoft jointly made this discovery, and listed out potential impact on application performance. The increased L3 cache latency affects performance of applications sensitive to memory performance. They also warn of a 10-15% loss in gaming performance. On the other hand, a dysfunctional "preferred cores" system would mean reduced performance in light-threaded tasks as the OS is unaware which are the processor's two best cores. Thankfully, both issues can be fixed via software updates, and AMD is working with Microsoft to push fixes for both issues through Windows Update, in an update rollout scheduled within October 2021.
141 Comments on AMD Processors Lose 15% Gaming Performance with Windows 11, L3 Cache Latency Tripled
Also, some network cards are apparently having issues, specifically Intel's Killer NICs, which is a bit ironic...
Microsoft really messed it up trying to please Intel.
Hence why this is only immediately noticeable on AIDA64's benchmark
/tinhat off.
Yeah totally no conspiracy or preferential treatmeant from Microsoft here...
not...something they noticed....when making this...revolutinary new OS?
not something they could have adressed when...making...it?