Clearly not, if the published data is correct. Somewhere between 6800 and 6800X seems possible.And the target is 6900XT level?
Clearly not, if the published data is correct. Somewhere between 6800 and 6800X seems possible.And the target is 6900XT level?
It'll be kinda game-dependent.Somewhere between 6800 and 6800X seems possible.
When exactly was the last time AMD being *not* the second-best?So hopefully the earlier rumors about two GCDs ultimately pan out, because while these small dies look great, they'd still end up second-best like Vega.
In single games it might reach a 6900XT, especially in RT. In a bigger parcour as Hardwareunboxed, it will land below a 6800XT, if not clocked much higher than 3ghz.It'll be kinda game-dependent.
So in some games It will be on the level of RX 6900(6950)XT and in others higher than RX 6800?It'll be kinda game-dependent.
Yeah, gotta wait out and see.In a bigger parcour as Hardwareunboxed, it will land below a 6800XT, if not clocked much higher than 3ghz.
Welcome to the "whole new uArch" deal.So in some games It will be on the level of RX 6900(6950)XT and in others higher than RX 6800?
Navi 33 with its 4096 stream-processors at ~3 GHz Game Clock should reach 24,6 TFLOPS, while Navi 21 / Radeon RX 6900 XT with 5120 stream-processors at 2015 MHz gets 20,6 TFLOPS. That's like ~20 % higher arithmetic performance. It's hard to imagine Navi 33 will be significantly slower than Navi 21 until RDNA 3 e.g. halves the ALU:TEX ratio (like Nvidia did with Ampere) or reduces the ALU:ROP ratio significantly.In single games it might reach a 6900XT, especially in RT. In a bigger parcour as Hardwareunboxed, it will land below a 6800XT, if not clocked much higher than 3ghz.
No one told you AMD engineering was sane.Seriously, do you people really believe that?
Hence why I've been shilling those parts for almost a year now, maybe more.That would be the first time in history that a company can increase compute throughput by 2.5x ( i guess AMD needs ~50% more transistor) while reducing the die size by 20% over the previous generation on a slighty better node.
Yep a bitter lesson from history. A 384-bit version with 16 CUs would simply have trashed GTX 280 and still would have been radically smaller (though about the same power consumption).While 4870/4850 were good designs, AMD would've been even better off with a bigger chip that would have give them the top-dog status for couple of years. Having the fastest cards during the 48-58 series would've gained them a lot of mindshare.
And that with 1/3 of the die. Seriously, do you people really believe that? That would be the first time in history that a company can increase compute throughput by 2.5x ( i guess AMD needs ~50% more transistor) while reducing the die size by 20% over the previous generation on a slighty better node.
nVidia doubled FP32 compute throughput only from Turing to Ampere but they used (inclusive every other improvements) 30% more transistors and a shrink von 12nm to 8nm (full node step).
So far it's causing confusion and not hype but whatever.Feeling major deja vu from the Navi3x hype
Would it be?And that with 1/3 of the die. Seriously, do you people really believe that? That would be the first time in history that a company can increase compute throughput by 2.5x ( i guess AMD needs ~50% more transistor) while reducing the die size by 20% over the previous generation on a slighty better node.
It's worse than that, I reckon, since RT explicitly relies upon math throughput in AMD's design (assumption based upon there being no sight of a re-design for RT in patent documents). So Navi 31 merely catches up to where it should have been in Navi 21 from day one...I mean with Nvidia pushing >30 Tflops in the same area as Navi 21 it is rather imperative for AMD to improve their FP32 flops/die area if they don't want to start falling behind again with shaders becoming more and more math heavy.
... while NVidia will be leaping far ahead again, it seems.That being said though Nvidia will likely be pushing ~40 Tflops from the same area in Lovelace so improving that by 2-2.5x won't lead to an AMD advantage in this metric still.
As far as I understand it with two SIMDs sharing a register file it's guaranteed to scale worse than RDNA 2 because any 3-operand instruction in one SIMD is going to interfere with the throughput of the other SIMD, even if only momentarily. Despite all the possible compiler jiggery-pokery we've seen in open source patches, we also know from history that relying upon the compiler is the best way to trash throughput.And yeah, with WGP rebalancing we can probably forget about RDNA3 scaling anywhere near linear along flops changes in comparison to RDNA2.
Don't forget that Navi 21 ⇾ Navi 33 (maybe increases arithmetic performance, but) reduces Infinity Cache by a factor of 4. Bus-with is reduced by a factor of 2. There were hints about simplified ROPs (some ops could be moved to ALUs) etc.
Yeap.We are talking about an archivement on the same process which laps anything TSMC was able to provide with their processes since years
And their CPU efficiency regressed.For example Apple has only improved efficiency by 20% with M2 GPU over M1
Navi 33 with its 4096 stream-processors at ~3 GHz Game Clock should reach 24,6 TFLOPS, while Navi 21 / Radeon RX 6900 XT with 5120 stream-processors at 2015 MHz gets 20,6 TFLOPS. That's like ~20 % higher arithmetic performance. It's hard to imagine Navi 33 will be significantly slower than Navi 21 until RDNA 3 e.g. halves the ALU:TEX ratio (like Nvidia did with Ampere) or reduces the ALU:ROP ratio significantly.
Only the shaders will be doubled compared to N23. The other stuff will stay the same.N33 -> 16WGP, 4096 Shaders, 128 TMUs, 64 ROPs, 32MB IC, 128bit GDDR6?
The other stuff will hardly stay the same, considering the Angstronomics article.