• 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 Speculation: Zen 4 (EPYC 4 "Genoa", Ryzen 7000, etc.)

Page 443 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Vattila

Senior member
Except for the details about the improvements in the microarchitecture, we now know pretty well what to expect with Zen 3.

The leaked presentation by AMD Senior Manager Martin Hilgeman shows that EPYC 3 "Milan" will, as promised and expected, reuse the current platform (SP3), and the system architecture and packaging looks to be the same, with the same 9-die chiplet design and the same maximum core and thread-count (no SMT-4, contrary to rumour). The biggest change revealed so far is the enlargement of the compute complex from 4 cores to 8 cores, all sharing a larger L3 cache ("32+ MB", likely to double to 64 MB, I think).

Hilgeman's slides did also show that EPYC 4 "Genoa" is in the definition phase (or was at the time of the presentation in September, at least), and will come with a new platform (SP5), with new memory support (likely DDR5).

Untitled2.png


What else do you think we will see with Zen 4? PCI-Express 5 support? Increased core-count? 4-way SMT? New packaging (interposer, 2.5D, 3D)? Integrated memory on package (HBM)?

Vote in the poll and share your thoughts! 🙂
 
Last edited:
If those scores are from the built in benchmarks, they have been shown as useless. The built in benchmarking tool was (at launch) giving out inaccurate numbers.

I don't know exactly where those screenshots come from but,

Hardware Unboxed goes out of their way to avoid using built in benchmarks.
 
I honestly admit that I would be surprised if AMD used Hybrid in the Low-Cost segment first. Maybe ADL-U is eating Rembrandt alive from a OEM cost/revenue proposal perspective.
Either way it sounds like a good idea to start with a monolithic design first in order to learn. Later on they might add mix'n'matched Zen4/5 and Zen4c CCDs.

If those scores are from the built in benchmarks, they have been shown as useless. The built in benchmarking tool was (at launch) giving out inaccurate numbers.

I would be surprised if AMD pursued the so called 'hybrid' or 'heterogeneous' strategy at all. They have no need to do so and keeping things simple means a single chip covers top to bottom. Zen4c is different because cloud providers will buy a ton of chips.

I strongly suspect that EPYC, Threadripper, and Ryzen will continue to share the same architecture along with the new high end mobile chips. THAT is how you bring costs down, improve profitability, and scale up in terms of performance.

Pretty funny you guys call Zen4+Zen4C a HYBRID thing.

Only if AMD feel extra pressure of E-core spam from Intel's xxxLake-S lineup. Since MeteorLake-S stays 16 E-core max, I don't think AMD has that pressure to use cloud/density optimized cores in HEDT. And I agree mobile is another story, Intel could crazily spam 2P+8E which would make AMD upset.

Anyway I would rather see official confirmation than a random anonymous or new user from internet.
 
Pretty funny you guys call Zen4+Zen4C a HYBRID thing.

Only if AMD feel extra pressure of E-core spam from Intel's xxxLake-S lineup. Since MeteorLake-S stays 16 E-core max, I don't think AMD has that pressure to use cloud/density optimized cores in HEDT. And I agree mobile is another story, Intel could crazily spam 2P+8E which would make AMD upset.

Anyway I would rather see official confirmation than a random anonymous or new user from internet.

I'm still having a big problem with seeing a 2 X Zen4 + 4 X Zen4C layout as even approaching the utility of a hybrid setup. It seems that just using a 6 core CCX with 8MB of L3 would accomplish the same thing without the die area hit of trying to break up the power domains and isolate scheduling. Zen4C is supposed to be feature complete with the regular Zen4 cores, just connected to a smaller L3 and using a denser process. Trying to run them both on the same CCD would kill any process benefit. I could see maybe doing a stack of two die that are optimized for different densities, or a tightly coupled tiny MCM with two different die. Heck, I could see a modified Mendocino die mixed with a 2 core N4 die for a 2 Zen4 + 4 Zen2 solution. The Zen4 CCD could be optimized as much as possible for performance without being overly large and the Mendocino modification could be modified as much as possible for power. In low power mode, the SerDes link could be completely powered down, and when performance is needed, burn the power as needed. Since it's a lower end solution, AVX-512 compatibility could be disabled without affecting desirability of the product.
 
why the heck is everyone just believing this new account?
Probably because 1. they say nothing that is unreasonable, 2. educated speculation already showed similar expectations and 3. we already had previous soft and hard leaks and info alluding towards similar things

Also, some people here vouched that they're not "just a rando" or troll. Which isn't to say that their info is 100% correct, but at least not malicious/clicks-driven.
 
5800X3D use 70-74W in games while the 7700X is at 72-77W, so it s no wonder that a theorical 7700X3D would see about no clock regression, beside the CPU voltage, that is lower than in the 5800X3D, wont be a limiting factor due to the added cache.

 
Probably because 1. they say nothing that is unreasonable, 2. educated speculation already showed similar expectations and 3. we already had previous soft and hard leaks and info alluding towards similar things

Also, some people here vouched that they're not "just a rando" or troll. Which isn't to say that their info is 100% correct, but at least not malicious/clicks-driven.
TBH, a mix of Zen4+Zen4c for low-cost is something that no one expected. Also there was only one single member vouching for credibility while at the same time refusing to give any reasoning.
In the bigger picture the information might pretty well be accurate. Until CES23 I will hold my breath.
 
TBH, a mix of Zen4+Zen4c for low-cost is something that no one expected. Also there was only one single member vouching for credibility while at the same time refusing to give any reasoning.
In the bigger picture the information might pretty well be accurate. Until CES23 I will hold my breath.
Well yeah, that one's the outlier. Heh

But WE DID KNOW "Little Phoenix" might be a thing tho. Just not about the potential heterogeneous config.
 
I'm still having a big problem with seeing a 2 X Zen4 + 4 X Zen4C layout as even approaching the utility of a hybrid setup. It seems that just using a 6 core CCX with 8MB of L3 would accomplish the same thing without the die area hit of trying to break up the power domains and isolate scheduling. Zen4C is supposed to be feature complete with the regular Zen4 cores, just connected to a smaller L3 and using a denser process. Trying to run them both on the same CCD would kill any process benefit. I could see maybe doing a stack of two die that are optimized for different densities, or a tightly coupled tiny MCM with two different die. Heck, I could see a modified Mendocino die mixed with a 2 core N4 die for a 2 Zen4 + 4 Zen2 solution. The Zen4 CCD could be optimized as much as possible for performance without being overly large and the Mendocino modification could be modified as much as possible for power. In low power mode, the SerDes link could be completely powered down, and when performance is needed, burn the power as needed. Since it's a lower end solution, AVX-512 compatibility could be disabled without affecting desirability of the product.

I think this will be an extremely low end, low cost, low power, monolithic design. Probably well under 100 mm2
 
AMD already has Mendocino that just launched to cover the low end so I don't see where a 2C/4C fits in unless it won't be released for quite a while.

I don't think Zen 4c is so much more area efficient than Zen 4 that it makes sense for AMD to design a weird 2+4 core combination instead of just releasing a 4-core Zen 4 chip unless this is acting like some kind of pipe cleaner product for AMD as well.

Why not just release an 8-core Zen 4c APU instead?
 
Also, some people here vouched that they're not "just a rando" or troll. Which isn't to say that their info is 100% correct, but at least not malicious/clicks-driven.

Seems to be mostly just the one person. And when asked why we should trust this new leaker, silence.
 
Seems to be mostly just the one person. And when asked why we should trust this new leaker, silence.
It's not like people with the in on the industry and sources would just... give us the name of the AIB they work for or the way they get private information out. 😅

A level of secrecy is needed.
At the end of the day one can have all the proof in the world, they could still doubt it. So it's not like knowing for sure before official announcements are made is a thing.

Anyway, apparently old school people from the leak-o-sphere like 'momomo_us' are retweeting their leaks like candy. For whatever that's worth.
 
AMD already has Mendocino that just launched to cover the low end so I don't see where a 2C/4C fits in unless it won't be released for quite a while.

I don't think Zen 4c is so much more area efficient than Zen 4 that it makes sense for AMD to design a weird 2+4 core combination instead of just releasing a 4-core Zen 4 chip unless this is acting like some kind of pipe cleaner product for AMD as well.

Why not just release an 8-core Zen 4c APU instead?
You mean like "big phoenix"? That has, essentially, an 8 core Zen4c ccx.
 
Where are you getting that there's gonna be a 16-core Crestmont implementation of Meteor Lake?

a one month old leak




  Meteor Lake-S 22 (6 P-core + 16 E-core) + 4 Xe cores, TDP125W
  Meteor Lake-S 22 (6 P-core + 16 E-core) + 4 Xe cores, TDP65W
  Meteor Lake-S 22 (6 P-core + 16 E-core) + 4 Xe cores, TDP35W
  Meteor Lake-S 14 (6 P-core + 8 E-core) + 4 Xe cores, TDP65W
  Meteor Lake-S 14 (6 P-core + 8 E-core) + 4 Xe cores, TDP35W
 
Last edited:
No, that's normal Zen 4.
That's the part about the "Big" and "Little" Phoenix leak that confuses me so far:
Previous mobile APUs never had the normal Zen cores but ones with significantly higher density and L3$ cut in half. That's what I expected Zen 4c to be about.

Now the leak talks about both Zen 4 and Zen 4c as part of PHX2, both with L3$ cut in half compared to the respective "normal" version. Both should still have higher density, especially Zen 4 as it has to be ported from N5 to N4 anyway.

But for it to make sense to include both Zen 4 and Zen 4c cores there needs to be a significant functional difference between the two that makes using one decisively advantageous over the other based on specific workloads. Significantly cut down FPU as previously discussed perhaps?

So instead increasing the TAM by using the mobile core in the cloud market, it appears the cloud core is a distinct core design, doubling the amount of core designs per Zen gen.
 
PHX2 can't be monolithic, If It has Zen4 + Zen4c. Another thing is CCX.
Zen3,4 had a single 8core CCX, now we will have 2 pairs? One with 2 cores and the second with 4?
6 Zen 4 would do the same job without using up a lot of extra space.

That new guy looks trustworthy for me, doesn't look like he is Greymon55, but PHX2 is quite weird.
 
PHX2 can't be monolithic, If It has Zen4 + Zen4c. Another thing is CCX.
Zen3,4 had a single 8core CCX, now we will have 2 pairs? One with 2 cores and the second with 4?
6 Zen 4 would do the same job without using up a lot of extra space.

That new guy looks trustworthy for me, doesn't look like he is Greymon55, but PHX2 is quite weird.
Yeah, if you do rough calculation of GPU die size based on SP, it is around half of the size of PHX's GPU area. We don't know the exact die size of 2P+4E with 8MB L3, but should be half of PHX's CPU as well...
 
Back
Top