AMD will launch Zen4 desktop processors Aug/Sep. Naturally RDNA3 GPUs have to follow after that. At the earliest it's likely to be around Oct/Nov. So I expect the launch schedule for RNDA3/Radeon 7000 series will follow the same pace as Radeon 6000 series. If Apple is going to release its own W7900x, it'll be a long wait of another 12 months from now. MacOS (x86_64) driver support may appear a couple of months earlier, perhaps in Ventura 13.3 or 13.4.
MacPro8,1 will launch Fall 2022 and start shipping early 2023. This gives Apple plentiful time to avoid direct comparison between M2 Extreme GPUs and a potential W7900x (or even RX7900XT due to lack of MacOS driver) if it does matter to Apple (which I think it doesn't because Apple has a bigger problem).
Chuckle. When Zen4 launch in Sep it will actually ship. Going to get announced in Aug and ship/launch in Sep. When Apple "launches" is it one or two Quarters before you can get it. 'Launch' and can't buy the product is P.T. Barnum misdirection spin.
As far as RDNA3 order. Decent chance that the monolithic. RX 7600 will launch qucker than the 7800. It is significantly less complex to make. The die size probably isn't that much bigger than the N4 GCD (graphics complex die) and doesn't need 3D interposers and ultra precision packaging.
Leaked info so far:
7900 Q3 '22 (probably Q4 to actually buy in substantive volume ).
7800 Q1 '23. ( again likely a slide. Even more likely if initial demand bubble for 7900 soaks up MCD chiplets).
7600. Q4 '22 ( doesn't depend upon MCD or 3D interposer or more complex packaging constraints. Still on super mature N6 and mostly not competing for N5 wafer starts. ).
AMD flagship RDNA3 GPU reportedly has a small graphics die, but there is a reason The upcoming Navi 31 GPU reportedly features 350 mm² graphics die, significantly smaller than the rumored figures from last year. According to Greymon55, AMD Navi 31 GCD (Graphics Complex Die) is only 350 mm² in...
videocardz.com
The RX7900XT may not even be an option for the Mac Pro if the board sizes are out of strict PCI-e specs.
AMD is mainly trying to get the 7900 before Nvidia to "stick it to them" because Nvidia is probably going to struggle ( both with a larger glut of cards they dumped into the crypto-craze market that is about to reguritate on them. And also the throw perf/watt Nvidia is throwing out the window to post numbers to still capture the 'king of the hill' crown at any cost. ). The 7900 and 4090 are in a pissing contest to a large enough extent that they are largely going to remove themselves from the Mac Pro (even if Apple wanted to do drivers which probably don't. ).
Lining up the 7800 intel drivers with the new Mac Pro or not isn't a make or break timing issue. Apple shoveling the Mac Pro onto market before the the 7000 series arrives. That window is blown. Probably never was true even in pre-pandemic internal roadmaps. The notion that if Apple merely blocks the driver , that will disable any direct comparisons is goofy. If Davinci Resolve runs on both platforms then comparing. A to B is entirely possible. That is how multiple platform benchmarks work. And those multiple platform benchmarks exist.
In another thread today someone tossed out this link about how Intel was suffering in Perf/Watt against the M2.
A killer screen that kills the battery life.
www.theverge.com
It is pure "emperor's new clothes" time (and hypocrisy) to think that when the numbers don't favor the M-series that is all going to be hidden away and the new Mac Pro is going to get a free pass (only can compare it to multiple year old previous Mac Pro configurations).
The bigger problem for Apple's GPUs is clearly demonstrated in M1 series that its design/software is not scalable:
View attachment 2038900
We don't know what exactly caused the sub-par performance in higher core counts. It's perhaps lack of software optimisation. It's perhaps 'poorly' designed hardware that caused thrashing in translation look-aside buffer.
That is more indicative that there is something wrong with the Apple GPU hype train than anything wrong with the hardware. The expectation was created for perfect linear increases was lots of hope more than historical insight or industry exposure..
Broad range of Metal Geekbench scores.
The W6800X and W6800X Duo get about the same score. So scalable benchmark? Nope.
The 6800 and 6600 have a ratio of 'core' count of 1.88 (3840/2048) and score ratio of 1.62 ( 138267/85580) -13% drop across those two ratios.
The 6900 and 6600 have a ratio of 'core' count of. 2.5 (5120/2048 ) and score ratio of 1.95 (166946/85480 ) -22% across those two ratios.
There is drop off on AMD also. Can check OpenCL across AMD,Nvida,etc also. linear core inscreases don't perfectly scale with Geekbench. Not sure why there would be an expectation that there are no scalar components to even a mostly parallel benchmark.
Apple was obviously targeting M1 Ultra GPU at W6900x in their planning.
That is highly doubtful. Because it only worked for the narrow corner case they were they 'won'. Apple execs have made comments are several points of surprise at the results got out of the M1 early on. There is some stuff that worked better than they thought. They also likely didn't have exact 6900 numbers when designing the Ultra. The Ultra's GPU cores are exactly the same as the M1 Pro/Max GPU cores which launched even earlier than the Ultra did.
They are a slightly different than the plain M1 cores but not by much.
The Pro and Max GPU cores were vastly more likely designed to take the laptop GPU targets. Whatever they "happen to cover" with an Ultra was just relatively cheap 'gravy'. (yeah had to 'pay' with ultrafusion but the additional GPU core design cost is pretty close to zero. )
Same is likely true for this upcoming 'quad'. The GPU cores probably are no different from what is being rolled out to the laptops. The laptop space is the primary target and they 'reuse' what comes out for desktop.
And the unreleased M1 Extreme GPU was planned to be equivalent to two W6900x. Both didn't work out as planned. I would speculate M1 Extreme GPU would score the equivalent of ONE W6900x in GB5 Metal. It was perhaps one of the reasons not released to avoid any obvious embarrassment.
Piled higher and deeper flawed logic. The W6800 Duo is a bigger threat to the Extreme than the W6900X. The W6900X is more to suck the maximum money out of folks pockets. A 68 Duo is cheaper than a 69.
Two dies (with some cores turned off) cost less than just one fully enabled die? Probably not. ( 69 and 68 are the same die:
5120 Cores, 320 TMUs, 128 ROPs
www.techpowerup.com
just a difference in binning. )
The W6900X was an opportunity to goose even fatter profits out the Mac Pro ecosystem. It probably wasn't a target.
BTW, Metal 3 support for Radeon 5000 and 6000 series seem to be another indication that AMD GPUs won't be abandoned on Intel Mac Pro anytime soon.
How? First, the systems with 6000 series in them are no where near Vintage/Obsolete stage. Apple was still selling iMac 27" models while Metal 3 was in 'beta'.
Second, Metal 3 beings some efficiencies that are being deployed (or have been deployed ... Apple playing 'catch up') in other APIs already. A direct from storage to GPU API update? Join the club ( it is in DirectX and Nvidia APIs already). Some structure to support raytracing abstractions. Again join the club... already existed elsewhere.
Better debugging and tracing/profiling support? That is something should hold back? (again is it really any giant leap over what others already provide in their interfaces? )
Keeping the Metal API mostly the same across both ranges of legacy GPUs just makes Apple's job more earily in the larger scope. Lowers port differences costs on both "sides" of the macOS port. (lowers costs for 3rd party developers also doing "universal/fat binary" building. ). The bigger issue for "support" for the Mac Pro 2019 is if Apple leaks that "zero 3rd party GPU driver" constraint of macOS on Apple Silicon back over onto the macOS on Intel side as well. Nothing new on side A so therefore constrain nothing new on side B. That is going to be a very large expectation mismatch for lots of legacy Mac Pro users.