I'm sure he'll be back if Alder Lake reclaims the gaming crown. For at at least the few months until AMD's 3D V-Cache chips launch.And Leonidas has gone again.
I'm sure he'll be back if Alder Lake reclaims the gaming crown. For at at least the few months until AMD's 3D V-Cache chips launch.And Leonidas has gone again.
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...www.techpowerup.com
Seems like Ryzen loses a massive 10-15% in Windows 11, with increased cache latencies.
Zen3 was only 1-2% faster than Intel previously, so it seems that they could be behind in the double digits of percentages, compared to the fastest Intel CPUs, now.
Well, most people won't notice as most of the time they are GPU limited and not CPU limited.This is why you dont get new OS at release lol.
Pretty sure it's getting fixed
I'm sure he'll be back if Alder Lake reclaims the gaming crown. For at at least the few months until AMD's 3D V-Cache chips launch.
As good as Alder Lake may be, it may not perform so well on games because of memory latency issues. Same reason why Gen 11 often lost to Gen 10.
What release? It's still beta/pre-release...This is why you dont get new OS at release lol.
Pretty sure it's getting fixed
Amusingly, some of the rumours are the exact flip of that. Strong results in multithreaded and production workloads we've seen. Good single threaded in what I'd class as non-latency sensitive production workloads.Prediction: Wins in single-threading; loses in multi-threading.
Amusingly, some of the rumours are the exact flip of that. Strong results in multithreaded and production workloads we've seen. Good single threaded in what I'd class as non-latency sensitive production workloads.
There is room for gaming be meh there... but could easily be twitter BS.
Thanks for posting that. I think they announced this last weekend, but this thread went on without anyone even mentioning that AMD and Microsoft were working on it.
Thanks for posting that. I think they announced this last weekend, but this thread went on without anyone even mentioning that AMD and Microsoft were working on it.
Having said that, I've stayed clear of major Windows releases at a minimum of 30 days ever since I remember reading about an update that was deleting shit from people's hard drives. There is absolutely no substitute for real-world application of any sort; entropy always assumes control.
Release Highlights
- OpenGL error pop up issue fixed.
- Restores intended function and behavior of UEFI CPPC2 (“preferred core”) in Windows® 11 build 22000.189 (or newer) on AMD processors.
Are there any benefits in keeping CPPC enabled in BIOS for Zen 2 CPUs?
Are there any benefits in keeping CPPC enabled in BIOS for Zen 2 CPUs?
- For AMD processors with the “Zen+” or “Zen 2” architectures: Systems configured with AMD Chipset Driver 3.10.08.506 (or newer) should have the AMD Ryzen™ Balanced power plan selected and active in the Control Panel > Power Options interface.
FUCK INTEL!
It's incredible, next people will discover that you can "fix" this issue by fooling Win11 into believing you have a "GenuineIntel" CPU.
I'll be sticking to Windows 10 for a while longer still. I had already planned to do so because of how unfinished 11 is by comparison, but this just reinforces that notion.
I bet my ass that the drivers which talks to CPU are developed by people behind HW themselves, so I am not exactly surprised that AMD sucks in this regard. After all it was same with Win10 for a long time. I doubt that it's just MS issue. AMD is occasionally really bad in their SW ventures.
how in the world is this just becoming known to AMD/Microsoft with the release candidate?
I had Win11 for a while via the Insider program right from when it was available. So yeah, definitely agreed about there being no reason to "upgrade" to Windows 11 for a long, long while. Stupid amounts of bugs aside, it's just not a feature complete product. Not to mention the numerous design inconsistencies that will probably never be resolved.There's really no reason to upgrade to Windows 11, no real reason, only one is:
I doubt that the solution is tailored to intel at low level, my guess is that as with previous iteration, the low level is build by the Intel/AMD themselves and since Intel generally have far more man power it's ready sooner. I mean Windows 10 Scheduler sucked hard even year ago for AMD system, AMD fixed it over time, I don't doubt that it's going to be same.There's really no reason to upgrade to Windows 11, no real reason, only one is:
The audacity of some people...
The only real and relevant change in Windows 11 that it's a factor to decide to use it or not is the new scheduler tailor made to Alder Lake. If you have one of these new CPUs then you should use W11, if not you better stick with Win10.
It was always like this, Microsoft always preferred to prioritize how Intel CPUs worked since the fist dual core CPUs. There's not reason for this to be happening again, it's just an collateral effect of Microsoft again giving all priority and attention to Intel, if other's full be fucked by W11 bad behavior is just their bad luck.
This is unquestionable, W11 looks to be working on intended with Intel CPUs, the Thread Director that Intel inserted on Windows 11 is working as it should... it it's own CPU only. This is what it's fucked, it's a result of Microsoft changing how W11 works by Intel's request.
Wrong choice of worlds.
It's us here, the users, outside of all this that are only knowing now.
This was reported in the Feedback HUB very VERY early on in during the Insider releases. Literally months ago. There was also a more generic "loss of performance" report in the Hub before it was narrowed down to the L3 cache issue. I've also seen it reported on Reddit quite a few times before release and how it was never fixed week after week of new Insider builds.MS comes up with a new version of Windows. Sends out insider and developer preview versions of the OS for testing. AMD, NVIDiA, Intel et al are fully in the loop. Performance impacting issues like this should have been discovered by AMD and escalated for attention.
how in the world is this just becoming known to AMD/Microsoft with the release candidate?
This was reported in the Feedback HUB very VERY early on in during the Insider releases. Literally months ago. There was also a more generic "loss of performance" report in the Hub before it was narrowed down to the L3 cache issue. I've also seen it reported on Reddit quite a few times before release and how it was never fixed week after week of new Insider builds.
They knew. Neither of them said nor did anything until the OS was RTM. And if they were doing anything, neither of them said a damn thing about it. Both MS and AMD are equally to blame here.
Win11 doesn't give nothing new for gamers, just change number from 10 to 11I'll be sticking to Windows 10
how did noone catch this in beta?
Prolly because same people who did beta for Battlefield 2042 and just thought the performance loss was a feature and wrote it off as 'ItS JuSt A bEtA'
This was reported in the Feedback HUB very VERY early on in during the Insider releases. Literally months ago. There was also a more generic "loss of performance" report in the Hub before it was narrowed down to the L3 cache issue. I've also seen it reported on Reddit quite a few times before release and how it was never fixed week after week of new Insider builds.
They knew. Neither of them said nor did anything until the OS was RTM. And if they were doing anything, neither of them said a damn thing about it. Both MS and AMD are equally to blame here.
So, despite everything, according to this video, W11 appears to be up to ~5% faster (HU's words) over W10 on AMD CPUs now. Interesting..
That's untrue. For instance it has AutoHDR out of the box available. For W10 you need to download some insider build, at which point you could as well just upgrade to 11 altogether.Win11 doesn't give nothing new for gamers, just change number from 10 to 11
An early build of the fix was starting to be tested through the Insider Dev channel just a few weeks prior to the public release. The update was unfinished and totally untested at that point. You can even see reports from people showing that the fix didn't necessarily work for them and it did not work as well as the public release eventually did.The testing builds were already being fixed but Microsoft released an older version without those fixes because AMD CPUs aren't a priority.