Tuesday, October 12th 2021
First Windows 11 Patch Tuesday Makes Ryzen L3 Cache Latency Worse, AMD Puts Out Fix Dates
Microsoft on October 12 put out the first Cumulative Updates for the new Windows 11 operating system, since its October 5 release. The company's monthly update packages for Windows are unofficially dubbed "patch Tuesday" updates, as they're scheduled to come out on the second Tuesday of each month. Shortly after Windows 11 launch, AMD and Microsoft jointly discovered that Windows 11 is poorly optimized for AMD Ryzen processors, which see significantly increased L3 cache latency, and the UEFI-CPPC2 (preferred cores mechanism) rendered not working. In our own testing, a Ryzen 7 2700X "Pinnacle Ridge" processor, which typically posts an L3 cache latency of 10 ns, was tested to show a latency of 17 ns. This was made much worse with the October 12 "patch Tuesday" update, driving up the latency to 31.9 ns.
AMD put out a statement on social media, which surfaced on Reddit. The company stated that patches for the two issues have been developed, and specified dates on which they'll be released. The patch for the Preferred Cores (UEFI-CPPC2) bug will be released on October 21. Customers can request the patch even earlier. By "customers," AMD is probably referring to big enterprise customers running mission-critical applications on Threadripper or EPYC-powered workstations. The L3 cache latency bug will be fixed through the Windows Update channel, its release is scheduled for October 19.If rumors surrounding the late-October/early-November launch dates of 12th Gen Intel Core "Alder Lake" processors are true, then the situation with these patches will have a direct impact on AMD. Processor reviewers will be compelled to use Windows 11 for their Core "Alder Lake" testing, as the new operating system supposedly has greater awareness of the heterogeneous core design. The switch to Windows 11 will force a re-bench of all processors, including the AMD Ryzen chips. With AMD cautioning of an up to 15% performance hit from the added cache latency and Preferred Cores bugs, results of AMD processors in 12th Gen Core launch reviews could be affected. It is advisable for AMD to reach out to the press with these patches immediately, if they are ready.
Source:
destiny2sk (Reddit)
AMD put out a statement on social media, which surfaced on Reddit. The company stated that patches for the two issues have been developed, and specified dates on which they'll be released. The patch for the Preferred Cores (UEFI-CPPC2) bug will be released on October 21. Customers can request the patch even earlier. By "customers," AMD is probably referring to big enterprise customers running mission-critical applications on Threadripper or EPYC-powered workstations. The L3 cache latency bug will be fixed through the Windows Update channel, its release is scheduled for October 19.If rumors surrounding the late-October/early-November launch dates of 12th Gen Intel Core "Alder Lake" processors are true, then the situation with these patches will have a direct impact on AMD. Processor reviewers will be compelled to use Windows 11 for their Core "Alder Lake" testing, as the new operating system supposedly has greater awareness of the heterogeneous core design. The switch to Windows 11 will force a re-bench of all processors, including the AMD Ryzen chips. With AMD cautioning of an up to 15% performance hit from the added cache latency and Preferred Cores bugs, results of AMD processors in 12th Gen Core launch reviews could be affected. It is advisable for AMD to reach out to the press with these patches immediately, if they are ready.
157 Comments on First Windows 11 Patch Tuesday Makes Ryzen L3 Cache Latency Worse, AMD Puts Out Fix Dates
edit: The CPU is AMD 3600 @ PBO +200
They seem aware but unwilling to push the fix on time for some weird reason.
patches that make it worse when the fix is already on the dev channel?
Right before windows 11 is required to review alder lake CPUs?
If it's not malicious, its massive incompetence.
I'm sure their BETA testers have tested it before release, oh wait...
At least they are honest about their lack of priorities.
What IS suspect is how a perfectly fine scheduler just suddenly "broke" right before alder lake came out. How the "patch" fixing this on dev branch is taking far, far too long to make it to stable. It's beyond explanation at this point.
Since the OS clearly doesn't work on that hardware I only have a simple question... what the hell is Microsoft trying to create?
The code they are trying to put together seems to have been mislabeled somewhere as it's not even close to what people expect.
Anyone with an IQ that even registers on the scale can tell this isn't working.
Intel sat on their hands for years and did nothing but put out 14nm+++++++++++++++++++++++++++++++ revisions and even they eventually moved to another node, albeit they didn't like the rules of the naming scheme or couldn't match it, so they change the rules/names.
Maybe, one day, Microsoft will catch on and put out a revision that sort of works, wait, we already have Windows 10. Not awesome but it at least works for the vast majority of people most of the time.
Microsoft Windows 11+++++++++++++++++++++++++++++++ here we come, er, eventually.
But hey, Intel's Alder Lake seems smooth as butter and puts AMDs offerings to shame. Wait, AMD can't reliably run the same benchmarks on the same OS.