- Mar 3, 2017
- 1,747
- 6,598
- 136
Like databases?AMD basically invited Intel to eat their lunch in parallel workloads with heavy inter-thread traffic.
"...significantly more hectic clock behavior under rapidly changing loads", said Igor Wallossek; emphasis mine. Very quick adaption of the clock to different loads should generally be regarded as a good sign.IgorsLab noted "hectic" CPU clocks during testing:
I don't now if it was a cause or just a symptom:Have we found out exactly why AMD delayed the launch? Related to the Windows/Linux disparity?
The photo was from an ES/QS(?), not from a retail CPU.Correct me if I'm wrong, but didn't we have screenies of misprinted IHSes on Zen5 CPUs?
Could this cause these cache line bouncing tests to regress?BTW, there are changes in the prefetch logic across L2 and L3 in Zen 5. Not sure if the motivation is to enable it to work better in different configurations but it might have added some regressions
Could be to handle bigger CCXs sharing L3 and snooping other CCXs
Yeah. Few examples:Like databases?
Or this might have been a deliberate choice, as Intel at some point basically nuked legacy 'mixed-mode' avx/sse with some changes to how VZEROUPPER works. AMD clearly doesn't care about anything non-enterprise related, so they might have tweaked interconnect in a way that makes it work really bad with 'legacy' desktop IO die (and maybe it works okay with the new epyc IO die)If AMD is unable to fix these issues, either via AGESA or a new stepping,
If these issues are also present in 9950X3D, I will be skipping Zen 5 and waiting for Zen 6.so they might have tweaked interconnect in a way that makes it work really bad with 'legacy' desktop IO die (and maybe it works okay with the new epyc IO die)
It'd be nice if some owner could have run this latency benchmark (either the one Dom used or the one CopeframeX created) in some non-Windows OS or in Win10 instead of Win11 (which all of reviewers seem to use)Surely this significantly higher inter-CCD latency is some software related issue and will be fixed?
Yeah, @Det0x could certainly try Win10 to see if it's a Win11 specific issue.It'd be nice if some owner could have run this latency benchmark (either the one Dom used or the one CopeframeX created) in some non-Windows OS or in Win10 instead of Win11 (which all of reviewers seem to use)
Is it possible to run benchmarks without installing the chipset drivers?My earlier run was on a old win10 21H2 v19044
View attachment 105379
Zen 3+1%
Haven't watched it yet. Zen 5 30% IPC incoming!
Didn't watch it also, but maybe admin mode just force-disables VBS and/or HVCI ? Not sure if reviewers disable both while testing, both hurt Zen3 and onwards gaming performance substantially (like 10% in some cases)Haven't watched it yet. Zen 5 30% IPC incoming!
I watched it, the TL;DW is:
Haven't watched it yet. Zen 5 30% IPC incoming!
It's a good thing you find a program that can crash your new hardware, that's the point of stress testing. Unless the program is made with illegal sequences of instruction which we know this isn't, then it's your hardwareAlso, tried Linpack Xtreme but it reports hardware failure within a minute or starting, think this program has not be refined for Zen 5 at this point in time.
I watched it, the TL;DW is:
The workaround improves gaming performance of Zen 5 by 4%, but it also improves gaming perf by 3% for Ryzen 7xxx series, so it's more like a Ryzen specific problem, not an issue related to Zen 5 alone.
It will also be patched in windows apparently.
So doesn't really change anything regarding when comparing Zen 4 and Zen 5
The workaround may also work for Intel so it may not be a Ryzen issue. Noone has tested this yet.The workaround improves gaming performance of Zen 5 by 4%, but it also improves gaming perf by 3% for Ryzen 7xxx series, so it's more like a Ryzen specific problem, not an issue related to Zen 5 alone.
It may not even be Ryzen specific, HUB just didn't test any Intel chips, only Ryzen 7700X and 9700X.so it's more like a Ryzen specific problem, not an issue related to Zen 5 alone.