Apple said M1 Ultra completes the M1 family. So it should not surprise anyone that M2 is on the horizon. On the other hand, it will be very surprising if the introduction of M2 starts from a Mac Pro with potentially the highest-end M2.
It could. If the M2 is just TSMC N5P process (like the A15) there is not much of a big blocker in doing a large die solution first and then mid size (or smaller ) versions later. It is a relatively very mature fab process so can make big affordably. The bigger issues would be whether they were running into wafer start competition with the A15 or A16 (if on TSMC process that is matched to ).
Similar issue If the Mac Pro waits for M3 (and TSMC N3? ) process. Could use a $6-8K package as a pipe cleaner for the process node ( lower volumes but far higher package prices to pay for all the 'defect' dies. )
Always smallest to biggest doesn't really make sense when the Fab processes iterate at a 18-22 month rate (Moore's law with some slow down). Sometimes the big dies can go first and pipe clean the process and some time the little dies can go first and do the same thing. The A-series and 'plain' Mx don't always have to play the bleeding edge process role. The yearly schedule of the A-sereis means they can't match that 18+ month cycle at all over time on each year.
If M2 is just TSMC N5P though it doesn't make sense to me for the very large dies at all though when N3 isn't that far of a wait. Apple could either make the Ultra just one incrementally larger die (at better Perf/Watt than using UltraFuion) or an easier package with closer to mid-sized dies.
If M2 is a TSMC N4 variant like the A16 then initially skipping the Pro/Max and doing a M2 and a relatively low volume M2 Ultra could make sense. The N4 is really a N5 tweak with some incremental density improvements for a limited set of things.
The plain M , Pro/Max , and Ultra are in different Mac Products that likely come out at different rates over time. ( Mac Pro 2010 [fake 2012 ] -> 2013 -> 2019 is no where near even 2 year cycles. That is probably not going to change with transition to Apple Silicon. That was basically primarily Apple effort/priority allocation all along. Not Intel's. )
But other than this, I don’t see many other ways for an Apple Silicon Mac Pro to have more than 128 GB of RAM. The 128 GB limit of M1 Ultra just doesn’t seem “pro” enough to me.
Seem "Pre enough" for Apple. At the Studio introduction there were comments as to 128GB was a "insane" , "extreme" amount of memory. Now, they are trying to skew the context to "insane" for a GPU direct access. But the SoC is basically a GPU with some other stuff wrapped around it. The core infrastructure there is primarily for the GPU , NPU , ProRes; not the CPU cores.
In 2023 or 2024 they'll probably take any 'easy' 256GB jump, but I doubt they are in a hurry to go through gyrations (and higher Perf/Watt) to get there.
For folks with 500GB data sets even 256GB isn't "pro enough". I suspect Apple has a pretty good idea of how many folks they are 'cutting off' with a 128GB limit. Given the iMac Pro went up to 256GB it is a bit low even without shifting to the modern upper Mac Pro user base.
Apple's bigger problem solution would be getting to 128GB more affordably than cranking out a 256GB prices that will just drive away even more classic Mac Pro userbase. The non modular memory is going to piss off a number of those folks and the 'Apple tax' prices will do even more. Apple's hope is that get into a 100-200GB of HBM2/3 versus Apple "poor man's HBM" kinds of value comparisons.
I guess we can only wait and see. If sometime in the summer or early fall an M2 MacBook (or Pro) appears, then a Mac Pro with the highest-end M2 in the end of the year would appear much more natural.
I'd doubt there will be M2's before Fall at this point. The upper Mini and Mac Pro are still on Intel. At least one of those is probably next off the board (probably the mini) . The overall breadth of the M-series line up probably isn't going to be at the same pace. Or even touch each generation.
The last several A__X iterations just went on the evens when has a full fab process node upgrade available. (enough a density increase to add some hefty upgrades ... not relatively small tweaks around the edges of performance).
M2 generation could be just M2 and M2 Pro. Then roll the M3 sequence out in 'reverse' order. Extreme , Ultra , Max/Pro , 'plain' M3. Go to another limited subset on M4 and they a broader range on M5 generation.