• 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.

Question Zen 6 Speculation Thread

Page 413 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
you're posting random people off twitter.
might as well check out my account instead.
People would if you made your account more like, I dunno 5 years ago! Too tricky to get to the biggest now which l, I know is by design. Can't be caught on the morning commute browsing...

Also since when was karlo a leaker 🙂?

Though very curious what that bad news is...anyone know?
 
People would if you made your account more like, I dunno 5 years ago! Too tricky to get to the biggest now which l, I know is by design. Can't be caught on the morning commute browsing...
Nothing you can't solve with Samsung Galaxy(tm) S26 Ultra.
Turn the thingy on and enjoy Hasumi massives in private (in public).
Also since when was karlo a leaker 🙂?
Everyone leaks on twitter now.
 
Zen4 4dense
Zen5 5dense
Only 6 dense
I could be wrong, but is the 'minimum core count' for Dense cores the only thing left to figure out?
 
No idea but if you ask me to guess 128C
I wouldn't rule out lower core count SKUs.
Not so much for yield reasons (though it may allow them to salvage a couple more bad CCDs), but because some customers may want something like "32 cores with as much non-X3D L3 as possible".
I mean, judging by desktop X3D models, VCache does seem to have some negative effect on failure rate and longevity, so not every server customer who cares about cache-per-core may want to risk using -X models.
Plus, it's a cost adder.
So I imagine having at least 1 64C and 1 32C SKU on SP7 may be a win-win for both AMD and some niche customers.

One SKU (maybe the 32C, or even a 16/8C SKU below?) with half the L3 disabled, to salvage even dies with too much dead L3, is also a possibility I guess.
 
  • Like
Reactions: 511
No idea but if you ask me to guess 128C
That won't be minimum, no way they'll avoid making ~64 cores, for licensing purposes there will certainly be high freq ~32-ish cores too.
I mean, judging by desktop X3D models, VCache does seem to have some negative effect on failure rate and longevity
That's due to voltage pushed way too high by consumer motherboards, they clocked it too high for vCache.
 
Last edited:
Interesting observation from the 9950X3D2 Thread:
Many AI / Inferencing Benchmarks scale well with V-Cache (e.g. oneDNN). This might be one of the reasons, why they opted for 4MB/Core L3$ for the 32C Zen 6c Chiplet. And I assume that when you put more demanding load on the CPU cores (not only web/microservices) additional cache will help as well.
 
Interesting observation from the 9950X3D2 Thread:
Many AI / Inferencing Benchmarks scale well with V-Cache (e.g. oneDNN). This might be one of the reasons, why they opted for 4MB/Core L3$ for the 32C Zen 6c Chiplet. And I assume that when you put more demanding load on the CPU cores (not only web/microservices) additional cache will help as well.
And Z7 dense bumps it to 7MB/core.
There really is nothing else like it.
 
also, those who pay licenses by core count and don't need 128 cores.

If you're running Oracle you want the most performance possible per core to minimize your total license costs. So if you can squeeze a few hundred MHz sustained frequency and have more L3 per core with a smaller config you'll come out well ahead on TCO with 4x the number of 32 core blades vs 128 core.
 
Back
Top