The rollout of Windows 11 has been fairly quiet, which is n’t surprising considering the small number of PCs that are entering it or are compatible with it. Inharmonious computers do n’t indeed get the upgrade, so Microsoft is virtually gatekeeping the upgrade anyway. That said, effects are n’t as quiet over at the AMD camp with verified performance issues with some supported CPUs, a problem that was ironically aggravated by Windows 11’s first Patch Tuesday.
There were two performance- related issues that AMD verified last week. The first is related to AMD’s “ preferred core” point that prevents certain CPUs from diverting processing vestments to advanced- performance CPU cores. The other saw a significant increase in quiescence on the generally fast L3 cache, which results in an overall pause in data read, write, and transfer pets.
The good news is that both Microsoft and AMD have conceded the issues and have promised fixes as soon as possible. The bad news is that for at least one of the problems, effects have just gotten worse after Microsoft rolled out Windows 11’s first set of updates. Now the L3 cache quiescence on affected AMD CPUs is nearly three times worse than ahead.
According to TechPowerUp, its Windows 11 system running on an AMD Ryzen 7 2700X showed a31.9 ns quiescence after the patch compared to 17ns last week. The Windows 10 quiescence for the same processor was only 10ns for comparison. Heise echoes this observation on its Ryzen 5 5600G, with an L3 cache quiescence of 40ns after Patch Tuesday versus12.4 ns on Windows 10. Those might be small numbers, but the emulsion effect on memory operations is relatively substantial. According to Heise, Windows 10 had a read outturn of 333 GB/ s while Windows 11 benchmarked at only 96 GB/s.
Another fix for this L3 cache problem is anticipated for coming Tuesday’s update. AMD, on the other hand, will be rolling out its own favored core patch on October 21. While upgrade interruptions are n’t exactly out of the ordinary, it’s still puzzling that such a severe performance bug could get once unnoticed, given Microsoft has formerly limited the number of supported processors for Windows 11 to a small number in the first place.