• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)

Page 668 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Is there a chance Strix Halo would outperform 9950X for membw bound workloads?

Does anyone happen to have numbers for theoretical membw for Strix Halo vs 2:1 DDR5 ~8000 on Zen5 DT?
 
My best guess is that the Yields just aren't there. 5.4 and 5.5GHz kinda works, so the 2 small SKUs can Release on 8th, but the number of 5.6 and 5.7GHz CCDs is so low that it would've been a paper launch.
Going from how omnipresent the 9900X is in marketing and product listing leaks, and the first early review also being on a 9900X, I very much doubt that.
 
Sadly, the only ones rejoicing at AMD's recall are Intel users who get more time to NOT get depressed upon seeing Zen 5 benchmarks.
With all the 13 and 14th gen degradation stories that are going on they have enough to worry about with their own rigs to be concerned with AMD.
 
That’s not what hardwareluxx is reporting. It’s also a hardware issue.
They are guessing. They see AMD recalling all units and announcing that they're replacing it with a fresh batch and jump to the conclusion that it must be a hardware issue.

But that's not necessarily the case. The "didn't go through QA" explanation works just as well. It's simply faster to recall and send out the next batch of products, which this time already went through QA. They can then without pressure reopen the recalled units and do the QA for them, which certainly takes more time.
 
Is 3600uclk and 2400fclk possible or is the italian guy delusional ?
I already gave my opinion in post #16459

I can accept he thinks he is running 2400mhz FCLK and/or buggy bios is showing him 2400mhz FCLK, but i dont think the system is actually running that in reality..
But its also very easy to prove me wrong, he just could post some read/write/copy numbers from aida or even better clam cache/mem benchmark @ 2000mhz, 2200mhz and 2400mhz FCLK so we could see the scaling (he have no NDA right?)
(Zen4 and now Zen5 is pretty much all bandwidth limited by FCLK)

He can use this is a comparison for what maxed out 2200mhz FCLK on a dual CCD cpu should look like (12 vs 16 core count show not matter in this regard)

6600MT/s 1:1
1721931578584.png

8000MT/s 2:1
1721928578770.png
 
Last edited:
So Italian dude with 9900X runs a few gaming tests with a "questionable" memory setup and thats it? Radio silence since then? At least throw us some more crumbs, bro, even stale ones, lol. People better hope I never manage to snag such an early unit and not be under NDA like him. There would be a lot of pissed off tech news outlets out there...:laughing:
 
Yes because then most "cheap" AMD users wouldn't want the extra cost being passed onto them. And the cost got driven high due to Apple.
TSMC dictates the prices not Apple. Anyway, if you believe so show some proof that that Apple is increasing the price of TSMC nodes.
 
So Italian dude with 9900X runs a few gaming tests with a "questionable" memory setup and thats it? Radio silence since then? At least throw us some more crumbs, bro, even stale ones, lol. People better hope I never manage to snag such an early unit and not be under NDA like him. There would be a lot of pissed off tech news outlets out there...:laughing:
Funny thing i got hands on 5600x on 31th oct 6days before official release. And litteraly noone was interested back then xD I think i only got a mention on VC or WCFKEK 😀
Look at the date https://valid.x86.fr/rsf5p1
I asked the italian guy if he can show aida64 with 2400fclk or come here on the forum xD
 

Attachments

  • EloQ-b8XYAAIpzD.jpg
    EloQ-b8XYAAIpzD.jpg
    131 KB · Views: 31
The first rule of fight club/CPU forum is attack the post not the poster. No personal attacks.
With no official reviews performed with potentially defective units and no retail sales to consumers of potentially defective units, there's very little reason for transparency. AMD has not "wronged" anyone, only delayed a product release a short time. They very well could have delayed it with no statement at all.
Is AMD paying you for your statement? Or are you an AMD voluntary public service agent here on the forum?

Hans, you are not supposed to JUMP out of Nakatomi Plaza. One week vacation. Aloha!

Mod DAPUNISHER
 
Last edited by a moderator:
It's called transparency.

Should every company always put out a statement and compare measurements every time they find an issue with an unreleased product? What a weird request. No one is owed "transparency" for all the work, debugging, and validation that happens with unreleased products. AMD said they discovered an issue (in testing), it's been resolved, and good product will be delivered with a very small delay. As long as the released products are good, there will be nothing to add to the story.
 
TSMC dictates the prices not Apple. Anyway, if you believe so show some proof that that Apple is increasing the price of TSMC nodes.
It's common sense logic. Who buys up capacity in bulk, years in advance and who has loads of cash and still makes loads more through their uniquely demented userbase? Out of all of TSMC's customers, that's Apple. They may have done a service to mankind by enabling TSMC to do accelerated R&D for the invention of advanced process technologies because of Apple's needs but they are also the ones who promoted TSMC to becoming a monopoly. Apple is like oxygen. A necessary evil. Too much leads to oxidation and accelerated aging and not enough halts future progress. I love *some* things about them but I hate way more about them than I love about them.
 
Back
Top