to the whole its a minor issue.
most use cases wont get a meaning issue. So they can fix it post launch.
Either:Windows 11 has been in beta testing for many months, with 10s of thousands of insider users which I am sure is a mix of both AMD and Intel chips. How was this not a known issue during the insider testing?
as it should......zen 3 was rival to 11th gen.it's already spread around the internet how alder lake is "much" faster than ZEN 3,
doubtful.if AMD telling the truth then it's so much worse than you think
They don't need to speed up Win 11. Much easier to slow down Win 10 in the next update. Oh, the joys of monopoly!
The only solution is to split up Microsoft, Apple, Facebook, Amazon, and all other companies, including those from cosmetics, energy, health sectors, having a disproportionate share in any market.
as it should......zen 3 was rival to 11th gen.
zen 4 will be rival to 12th gen. (and given how upcoming zen3 updated chips can net you large performance increase there is no reason to doubt zen4 wont be a great chip line)
doubtful.
WIN11 is changing way stuff is done and likely just a conflict somewhere and within month prolly be fixed. (most new WIN versions have issues with performance somewhere such is early adopters risk)
The L3 cache issue has been known since early in the public beta process. Here is a link to users reporting the problem back in July.Windows 11 has been in beta testing for many months, with 10s of thousands of insider users which I am sure is a mix of both AMD and Intel chips. How was this not a known issue during the insider testing?
And I'm wondering why that patch still not coming to this final version yet, if it exists.The L3 cache issue has been known since early in the public beta process. Here is a link to users reporting the problem back in July.
https://www.techpowerup.com/forums/...ry-benchmark-here.186338/page-67#post-4566501
For some reason, neither AMD or MS have acknowledged the issue until now. They've known about this for a while as it is already patched in developers builds of Win11.
Issues this low level on a system this complex take time to make sure that you aren't going to play whack-a-mole with bugs.And I'm wondering why that patch still not coming to this final version yet, if it exists.
The bug is present and solved, but not on official version. Doesn't make any sense to me.Issues this low level on a system this complex take time to make sure that you aren't going to play whack-a-mole with bugs.
Here's an analogy. Say an airliner found a crack in the body of a plane. It's fixable so they go ahead and patch it. Would you feel comfortable if they didn't do a series of tests to make sure the patch actually holds and put the plane back into service right away?The bug is present and solved, but not on official version. Doesn't make any sense to me.
Just my 2 cents.
The windows 11 team doesn't even know what a functional GUI looks like, which is crazy considering they have a half-dozen (well, more like 3) decent versions of Windows to use as a reference.
Can you really expect them to be able to code a scheduler when they still can't even figure out button placement, menu layout, or why Windows 8 was unusable?
At this point, they've been actively trying to remove the control panel for over 5 years... but they haven't even successfully copied that basic feature into a semi-functional settings menu. You would think that, at some point, they would have realized that the control panel is fine, and also that Windows doesn't need to compete with iOS.
Here's an analogy. Say an airliner found a crack in the body of a plane. It's fixable so they go ahead and patch it. Would you feel comfortable if they didn't do a series of tests to make sure the patch actually holds and put the plane back into service right away?
Granted lives aren't at stake here, but again, when you have something this low level in a system as complex as Windows, you kinda want to make sure the "fix" is actually a fix.
Then let me add: The crack was found during a routine inspection, which implies the plane was flying with it before.I would rather not fly with that crack, because we are flying with it. What an analogy......
In this case the crack was found even before the flight and that's the problem. The dev release that i'm talking about, was release before the original release and it doesn't have the bug.Then let me add: The crack was found during a routine inspection, which implies the plane was flying with it before.
But I mean, if you want to throw out a fix in software without thoroughly testing what it might affect, by all means, be that software developer. I'm sure everything will be fine. 😉
I don't know if you are talking to me, but if you are, you're wrong 😉I think they don’t understand how software gets tested before it gets released
You do? If so, please let me know, I would like to get my knowledge richer.It was left out of the official release for reasons you may not understand
It's not about time...WCCFTech recently reported that the fixes for the AMD Performance problems under Win11 are coming next week [Oct. 19 from MS with a new Win11 update and Oct. 21 from AMD with an updated CPPC driver]
AMD Ryzen CPU's L3 Latency Performance Fix To Be Resolved By Microsoft Through Windows 11 Update on 19th October, CPPC Driver on 21st
AMD will be issuing a fix to the performance degradation issues encountered with Ryzen CPUs in Microsoft's Windows 11 OS next week.wccftech.com