fastandfurious6
Senior member
- Jun 1, 2024
- 432
- 583
- 96
I am not convinced they will go back, after the big success of Zen 5 in this area (yes, most people don't see it, but some of us do), especially in servers.To be clear, it will still run 512-bit code, just at half rate. And using 512-bit registers is still a win, because it means frontend can do less work. Just like Zen4.
Improvements are also changes. Why would you like to deny us these?"Don't touch! Changes Forbidden".
x64 needs ubiquitous AVX512 more than 512-bit calculations.That's the cost of a future with ubiquitous 512-bit calculations.
Only for a few generations so that the developers get bored from lack of advances in FP performance and start optimizing their code to squeeze more performance out of the FP unitsImprovements are also changes. Why would you like to deny us these?
I have many Zen 4 computers, and servers, and also a few Zen5, including a Turin. The avx-512 performance is like 40% faster. So I would not want to lose that is what I am saying. I don't know the technical side, just how they perform.Improvements are also changes. Why would you like to deny us these?
x64 needs ubiquitous AVX512 more than 512-bit calculations.
I have many Zen 4 computers, and servers, and also a few Zen5, including a Turin. The avx-512 performance is like 40% faster. So I would not want to lose that is what I am saying. I don't know the technical side, just how they perform.
Yeah.
Medusa DT is h2'26, everything else is CES'27.
Obviously, server is earlier than that.
5-digit names were quite common in the 1980s and 1990s.5-digit nomenclature, was sort unprecedented, when it happened with Intel CPUs.
80386 my beloved....5-digit names were quite common in the 1980s and 1990s.
Incept?incept a baby
Halfed AVX512 is for power and cost limited scenarions. I do not see too much benefit of a full AVX512 implementation on consoles, because for many things you could just use the GPU (vector and matrix operations).
This is true but I would think Sony will use Zen 6c cores. Assuming they are still smallish I'm not sure it's worth the engineering effort to gut the FPU.
There is no engineering effort to gut the FPU, AMD has already designed it to be configurable. You just pick whether you want 256-bit or 512-bit ALUs, and I don't see a world where the die area would be better spent on doubling the SIMD execution width, and not in the GPU.
L2 is not configurable.Halfed L2$ (512kByte) ~0.5mm2 per Core (already included above)
Because L2 is physically not configurable.Why should it not for a semi-custom chip?
Given rumours put Zen6c server CCDs at 32C I'd say that they might be smoler than ever.Assuming they are still smallish I'm not sure it's worth the engineering effort to gut the FPU.
PS5 Pro already has 60 CUs.For the standard PS6, I am thinking more like 8 Zen 6c cores plus 60-80 UDNA CUs on N3P.
Yes the magic of gfx13. Next.UDNA would have to pull off some kind of magic to extract that much more perf from the same CU count in just a handful of years.
Ah yes SoIC for consoles. Genius.If AMD can make SED chiplet gaming GPUs viable with minimal/zero software problems then they can maybe make one die that can work for their halo APU segment and Sony can use 2x for PS6
PS5 Pro already has 60 CUs.
UDNA would have to pull off some kind of magic to extract that much more perf from the same CU count in just a handful of years.
PS4 Pro and PS5 had same CU count, but PS5 had more than 2x the clock speed.
PS5 Pro -> PS6 won't have anywhere near that kind of clock scaling headroom.