Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Ah I see your confusion. I wasn't suggesting that the logic dies would be vertically stacked - SoIC allows for both vertical and 2.5D interposer connects (as Apple already uses for its fusion connector).

Confused? You snipped out the leman quote that I was responding to which started off:

Looking at the wording from Apple patents describing stacked die solutions, a focus appears to be on increasing the effective transistor budget without increasing the package area.
previous to that my comment was in response to tenthousandthings comment

... We can assume Apple’s priorities haven’t changed. ...


Apple reportedly clearly lays out their objective and I'm confused because there is a disconnect between their object and your horizontal expansion proposals? If the length and width of the package is pragmatically fixed, that would be a constraint that Apple didn't want to abandon. The Max package really can't get too much bigger in the MBP 14" logical board.

AVfmWrPYUkdFd1uC.large




The Mac Studio has similar issue with a "double Max" solution for the Ultra. The Ultra's package really can't much bigger.

The die size and the package size are different. The pins to the off-package I/O just tend to take up more space. (so there has been some slop in dies growing while package stays the same time. )

My post is more theoretical about what Apple *could* use SoIC-mh for in the Pro and Max line as Kuo and Ma have both released notes suggesting that will be implemented - Kuo specifically in the M5 Pro/Max. If my memory is right he specifically mentioned the 2.5D connector, not 3D. If so, vertical cache is less likely for the M5 Pro/Max. Ma's note on the subject was from awhile ago and if memory serves merely mentioned that Apple would explore using tile-like structures for its Pro/Max line of chips for the M5/M6. This could be wrong of course.

The 2.5D connector is going to buy increased 2-D transistor density how? Let's say more the "I/O" intense stuff off to a N4/N5 die. The 2D area that the I/O is taking up isn't shrinking there ( might be slightly bigger since the smaller fraction of logic in the I/O subsystem might have gotten bigger when backsliding on fab process). If take the "just as big" I/O die and "just as big" logic die and 'glue' them back together with a 2.5D process did the area go down?
If shooting for a radical increase in performance, then probably not. The logic tile/chiplet probably grew a bit even with improved process node ( just as the path Apple has been on with Max growing larger and larger. )


Perhaps if Apple did a N3X logic-only die and a N3P 'the rest" die then perhaps the 2D footprint area could do down. The I/O die isn't so much getting 'cheaper'. It just is more flexible ( stays on Fin-Flex while logic only tosses that flexibility to focus primarily on getting smaller (e.g., reverse the bloat from previous generations). ). To get an aggregate package transistor density increase, it gets hard to include dies that significantly backslide on transistor density and still get a net increase if no stack. The 'other' die(s) with the increase has to make up the backslide deficit before get any net increase.

Apple working with Broadcomm to do a server SoC in 2027 (M6 like time frame) . If it was Max and server were sharing and bigger gaps on I/O that makes more sense to me. But the Pro, SoIC applied to that keeping the costs the same seems like a stretch. (very similr to the Rube Goldberg Mn Extreme rumors that looked more and more expense the more folks tried to push that rock up a hill in rumors. )
 
  • Like
Reactions: Moka Akashiya
Confused? You snipped out the leman quote that I was responding to which started off:


previous to that my comment was in response to tenthousandthings comment




Apple reportedly clearly lays out their objective and I'm confused because there is a disconnect between their object and your horizontal expansion proposals? If the length and width of the package is pragmatically fixed, that would be a constraint that Apple didn't want to abandon. The Max package really can't get too much bigger in the MBP 14" logical board.

AVfmWrPYUkdFd1uC.large




The Mac Studio has similar issue with a "double Max" solution for the Ultra. The Ultra's package really can't much bigger.

The die size and the package size are different. The pins to the off-package I/O just tend to take up more space. (so there has been some slop in dies growing while package stays the same time. )



The 2.5D connector is going to buy increased 2-D transistor density how? Let's say more the "I/O" intense stuff off to a N4/N5 die. The 2D area that the I/O is taking up isn't shrinking there ( might be slightly bigger since the smaller fraction of logic in the I/O subsystem might have gotten bigger when backsliding on fab process). If take the "just as big" I/O die and "just as big" logic die and 'glue' them back together with a 2.5D process did the area go down?
If shooting for a radical increase in performance, then probably not. The logic tile/chiplet probably grew a bit even with improved process node ( just as the path Apple has been on with Max growing larger and larger. )


Perhaps if Apple did a N3X logic-only die and a N3P 'the rest" die then perhaps the 2D footprint area could do down. The I/O die isn't so much getting 'cheaper'. It just is more flexible ( stays on Fin-Flex while logic only tosses that flexibility to focus primarily on getting smaller (e.g., reverse the bloat from previous generations). ). To get an aggregate package transistor density increase, it gets hard to include dies that significantly backslide on transistor density and still get a net increase if no stack. The 'other' die(s) with the increase has to make up the backslide deficit before get any net increase.

Apple working with Broadcomm to do a server SoC in 2027 (M6 like time frame) . If it was Max and server were sharing and bigger gaps on I/O that makes more sense to me. But the Pro, SoIC applied to that keeping the costs the same seems like a stretch. (very similr to the Rube Goldberg Mn Extreme rumors that looked more and more expense the more folks tried to push that rock up a hill in rumors. )
Yes, confused. Partly my fault as the original post didn't explicitly specify 2.5D vs 3D connections for the logic dies in part 3. My original post was written before @leman wrote anything, also I'm pretty sure @leman was not advocating that CPU and GPU logic dies would be stacked (if I remember Apple's patent he references correctly there might have been some I/O but it was mostly cache structures mentioned being 3D stacked - he can correct me if I'm wrong), and I didn't snip anything out. That's simply how Macrumors' post system works by default. When you reply to a post, quotes inside the quoted posts disappear. Same as when you replied to me, same as when I replied to you just now. As such, I understood where you were coming from and why you had gotten confused between my and @leman's posts, but I was saying your critique about 3D stacking of CPU and GPU dies didn't actually apply to what I had written originally.

For the post above, I have to admit that I'm a little confused by the package size critique in your post above. My proposal is not making the Max package size much bigger than it otherwise would be, just whatever additional width the interconnects take which would be negligible compared to the size of the component dies. What one could do with my proposal, is build more flexible solutions than the Ultra (most of which would be smaller!).

Let's do some concrete examples: If a Pro SOC would be made of 1 CPU die + 1 GPU die, then a Max would be 1 CPU die + 2 GPU dies* and an Ultra would be 2 CPUs + 4 GPUs. Same exactly as now, same basic size. However, because you now have (theoretically) the ability to combine any number of these dies together, you could make SOCs in between an Ultra and a Max such as 1 CPU + 3 GPUs or 2 CPUs + 2 GPUs or etc ... in theory you could even make a smaller "Max" with 2 CPUs + 1 GPU, good for a lot of devs. You could also make different Ultras than just a 2+4. Yes, you could in theory also make larger packages than the Ultra, but which still wouldn't be as big as the fabled "Extreme". The real problem here is logistics, which you and I already pointed out make actually offering a lot of such combinations extremely unlikely, especially as these would almost all be at the high end - Max or above. So while this would be awesome, I already said, even in my initial post, that one should temper expectations as to what Apple would actually offer here even if they introduce tiles, and I also agree with you that even if Apple were to offer more flexible configurations, one should also temper the expectations into what devices those larger SOCs could fit.

Again, Kuo and Ma are the ones asserting that the 2.5Ds packages are coming to the Pro and Max dies in the M5/M6 generation. Indeed, @tenthousandthings can correct me, but, especially Kuo's research note on the topic asserting that SoIC-mh is coming to the M5 Max/Pro, is why he posted what he posted - wondering if there might be performance benefits. Now, could Apple do any of this without adding extra flexibility to the end package? Of course! And that's more likely. For Apple it may be worth it to simply break out the SLC/IO onto a separate, cheaper die or do stacked SLC (the latter not quite fitting Kuo's note, but still plausible based on the tech). Those ideas, points 1 and 2 in my original post, are what @leman was referring to as "spot on", not my mixing and matching tiles stacked or not.

Also, depending on the precise manufacturing economics, even just building the Pro/Max/Ultra out of smaller dies than they do currently *might* be cheaper depending on package costs, yield, and die reuse. And thus Apple may simply offer the same solutions they do now just built out of smaller dies without offering all the variations that might, in theory, be viable but would, in practice, be a logistical strain. Lastly, naturally, Kuo and Ma could just be wrong. This is simply my take on the various ways Apple could reasonably implement advanced packaging for the Pro and Max chips (with some fun potential implications) if they are right.

*Alternant is a "Pro" die with 1 CPU + 1 GPU on it and then there exists a GPU die that gets tacked on to make a Max. A little less flexible but would have fewer interconnects, so potentially less expensive when building larger units (again depending on the economics of TSMC packaging and yields), also less power, etc ...
 
Last edited:
Let's use a M3 Max for visualization:
Above the red line is the CPU + I/O part and below are two more or less identical GPU + SLC + MI parts.
Keep in mind this is the original M3 Max from 2023 w/o Ultra-Fusion.

Apple M3 Max Die-Shot chiplet.png


The more chiplets there are the more additional connection areas nearly equivalent to Ultra-Fusion are needed.
Using smaller connection areas would lead to less connections, which would need to clock faster, and therefore be more power hungry.
My guess:
If Apple divides the Max die at the red line we will see two different "GPU dies", one for Pro and one for Max with the Pro GPU die being a design chop of the Max GPU die.
 
  • Like
Reactions: AshesXY
Let's use a M3 Max for visualization:
Above the red line is the CPU + I/O part and below are two more or less identical GPU + SLC + MI parts.
Keep in mind this is the original M3 Max from 2023 w/o Ultra-Fusion.

View attachment 2565041

The more chiplets there are the more additional connection areas nearly equivalent to Ultra-Fusion are needed.
Using smaller connection areas would lead to less connections, which would need to clock faster, and therefore be more power hungry.
My guess:
If Apple divides the Max die at the red line we will see two different "GPU dies", one for Pro and one for Max with the Pro GPU die being a design chop of the Max GPU die.
But that would mean the same CPU core counts (unless binned) for Pro and Max. Perhaps, just like your GPU dies, there could be two CPU dies? Maybe binning is enough, but not an ideal solution for CPU-heavy workloads that are happy with just an anemic GPU. Such workloads end up paying for an unused GPU, where more CPU would have been much better preferred.

Ideally chiplets should allow for building three types of configurations 1) CPU beast (max CPU, sufficient GPU), 2) GPU beast (max GPU, sufficient CPU), and finally 3) Balanced (good CPU, good GPU). One can also imagine 4) Ultra (max CPU, max GPU) limited only by max power.
 
Last edited:
I think the break up of the Max die into chiplets is primarily driven by the inevitable high-NA die size limit and Apple will use as few chiplets in a SoC as possible. Also Apple will try to keep the die size of each chiplet as close to half of the total die area as possible (for example CPU:GPU -- Pro = 60:40, Max = 43:57).
binned CPU chiplet + small GPU chiplet = Pro
non binned CPU chiplet + big GPU chiplet = Max
no CPU beast
no GPU beast
 
But that would mean the same CPU core counts (unless binned) for Pro and Max. Perhaps, just like your GPU dies, there could be two CPU dies? Maybe binning is enough, but not an ideal solution for CPU-heavy workloads that are happy with just an anemic GPU. Such workloads end up paying for an unused GPU, where more CPU would have been much better preferred.

Ideally chiplets should allow for building three types of configurations 1) CPU beast (max CPU, sufficient GPU), 2) GPU beast (max GPU, sufficient CPU), and finally 3) Balanced (good CPU, good GPU). One can also imagine 4) Ultra (max CPU, max GPU) limited only by max power.

I think the break up of the Max die into chiplets is primarily driven by the inevitable high-NA die size limit and Apple will use as few chiplets in a SoC as possible. Also Apple will try to keep the die size of each chiplet as close to half of the total die area as possible (for example CPU:GPU -- Pro = 60:40, Max = 43:57).
binned CPU chiplet + small GPU chiplet = Pro
non binned CPU chiplet + big GPU chiplet = Max
no CPU beast
no GPU beast
If advanced packaging is coming to the M5 Pro/Max, my guess is that this first iteration will be to move as much SRAM and wiring off the main die as possible onto ... let's call it the SOC die - basically a separate die for I/O, Display Controller, with maybe stacked SLC on the main die/SOC die - manufactured on a node behind the main logic die.

I included a 3rd more extreme approach, separating GPU and CPU tiles (or a Pro chiplet + GPU tile or @smalm's version of a CPU tile + two different GPU tiles), as a possibility because Apple certainly could do that and it could have some pretty fun implications. I do believe that something like that is likely coming eventually - as @smalm writes, eventually high-NA die size limits will come into play and while Apple will likely test the waters on that before they are forced to, that may be awhile. TSMC doesn't seem to be in a rush here.

If Apple were to adopt a more disaggregated tile design, would they allow some additional flexibility? I'd like to think so as it certainly is a major advantage of the approach. But of course there are still practical limitations beyond the technical ones (and a few technical ones too).
 
Last edited:
  • Like
Reactions: aaronage
Updated codenames - 09
Updated codenames - 10/05/2025

On https://theapplewiki.com/wiki/User:Ilikeiphone123/Playground/Codenames there are a lot of new information.

What is the most notable to me is that Apple seems to plan to release Pro/Max/Ultra chips at a slower pace than the regular M chips. Maybe Apple will release new Pro/Max/Ultra every 2 years instead of every year. This means no M6 Pro/Max/Ultra. Next release of the pro chips will be M7 Pro/Max/Ultra, codename Andros.

Those with "?" are my personal speculation

MarketingInternalCodenameCPID
A16H15PCreteT8120
M3H15GIbizaT8122
M3 ProH15SLobosT6030
M3 Max (14-core)H15MPalma CRT6034?
M3 Max (16-core)H15CPalma 1CT6031
M3 UltraH15DPalma 2CT6032
A17 ProH16PCollT8130
M4H16GDonanT8132
M4 ProH16SBrava ChopT6040
M4 MaxH16CBravaT6041
A18H17ATupaiT8140a
A18 ProH17PTahitiT8140
M5H17GHidraT8142
M5 ProH17SSotra ST6050
M5 MaxH17CSotra CT6051 ?
M5 UltraH17DSotra DT6052 ?
A19H18ATilosT8150a
A19 ProH18PTheraT8150
M6H18GKomodoT8152 ?
A20H19ABandaT8160a
A20 ProH19PBorneoT8160
M7H19GDelosT8162
M7 Pro ?H19SAndros ST6060
M7 Max ?H19CAndros CT6061
M7 Ultra ?H19DAndros DT6062
A21H20ANimosT8170a ?
A21 ProH20PNaxosT8170 ?


MarketingInternalCodenameCPID
S6, S7, S8M10TurksT8301
S9, S10M11CaicosT8310
S11 ?M12NevisT8320

MarketingCodenameCPID
C1Leda/SinopeC4010 ?
C2 ?Pandia/GanymedeC4020
C3 ?Isonoe/PrometheusC4030


MarketingCodenameCPID
R1BoraT6500
R2 ?CorfuT6502

sources:

 
Last edited:
We already have the M5 among us. Can’t wait for the first test and reviews!!!

EDIT: okay, Apple says the M5 is the next big leap in AI performance, with up to 4x the GPU ML/AI performance… that’s like a lot, isn’t it? I suspect this will be a new baseline for certain local MLL/AI features in the future…
 
Last edited:
Apple is marketing the M5 to be 1.6x faster than M4 regarding Gpu
If its true M5 can challenge M3 Pro

The is likely "up to 1.6X" faster. Probably not on every possible workload. Anthing that has more than a 32GB memory footprint is not going to hit that number.

Or it is an average uplift , which means some stuff is up and below that number by workload.
 
I guess they just go how the competition is doing, a 2 year cycle for top chips is probably what they always wanted but competition is there and keeping up. Base chips is probably still 70% sales if not more, but I hope competition will get stronger so they have to release :D
 
Updated codenames - 10/05/2025

On https://theapplewiki.com/wiki/User:Ilikeiphone123/Playground/Codenames there are a lot of new information.

What is the most notable to me is that Apple seems to plan to release Pro/Max/Ultra chips at a slower pace than the regular M chips. Maybe Apple will release new Pro/Max/Ultra every 2 years instead of every year. This means no M6 Pro/Max/Ultra. Next release of the pro chips will be M7 Pro/Max/Ultra, codename Andros.

Those with "?" are my personal speculation

MarketingInternalCodenameCPID
A16H15PCreteT8120
M3H15GIbizaT8122
M3 ProH15SLobosT6030
M3 Max (14-core)H15MPalma CRT6034?
M3 Max (16-core)H15CPalma 1CT6031
M3 UltraH15DPalma 2CT6032
A17 ProH16PCollT8130
M4H16GDonanT8132
M4 ProH16SBrava ChopT6040
M4 MaxH16CBravaT6041
A18H17ATupaiT8140a
A18 ProH17PTahitiT8140
M5H17GHidraT8142
M5 ProH17SSotra ST6050
M5 MaxH17CSotra CT6051 ?
M5 UltraH17DSotra DT6052 ?
A19H18ATilosT8150a
A19 ProH18PTheraT8150
M6H18GKomodoT8152 ?
A20H19ABandaT8160a
A20 ProH19PBorneoT8160
M7H19GDelosT8162
M7 Pro ?H19SAndros ST6060
M7 Max ?H19CAndros CT6061
M7 Ultra ?H19DAndros DT6062
A21H20ANimosT8170a ?
A21 ProH20PNaxosT8170 ?


MarketingInternalCodenameCPID
S6, S7, S8M10TurksT8301
S9, S10M11CaicosT8310
S11 ?M12NevisT8320

MarketingCodenameCPID
C1Leda/SinopeC4010 ?
C2 ?Pandia/GanymedeC4020
C3 ?Isonoe/PrometheusC4030


MarketingCodenameCPID
R1BoraT6500
R2 ?CorfuT6502

sources:

How reliable is this information? Like does this person Ilikeiphone123 have a track record? It seems he's saying he found the codenames in Playgrounds? Someone can confirm?

But let's go on a limb and say it's accurate (and not missing anything), it could be that Pro and Max chips are being pushed back this generation and there will be a gap next generation, but maybe a quicker update with the M7? So let's say Mar 2026 and then October 2027? Rather than releasing October 2025 and October 2027?

I have to admit I'm not sure I believe this - the rumor mill is that Apple will massively updating the M6 MBPs with all new chassis and screens, but if there are literally no Pro and Max chips then there is no 16" M6 MBP at all (and of course no Pro minis nor Studios that generation). So the only upgraded MBPs is the 14" with the base M6 chip. Hmmmm ... possible of course, but seems unlikely.
 
  • Like
Reactions: Rnd-chars
How reliable is this information? Like does this person Ilikeiphone123 have a track record? It seems he's saying he found the codenames in Playgrounds? Someone can confirm?

But let's go on a limb and say it's accurate (and not missing anything), it could be that Pro and Max chips are being pushed back this generation and there will be a gap next generation, but maybe a quicker update with the M7? So let's say Mar 2026 and then October 2027? Rather than releasing October 2025 and October 2027?

I have to admit I'm not sure I believe this - the rumor mill is that Apple will massively updating the M6 MBPs with all new chassis and screens, but if there are literally no Pro and Max chips then there is no 16" M6 MBP at all (and of course no Pro minis nor Studios that generation). So the only upgraded MBPs is the 14" with the base M6 chip. Hmmmm ... possible of course, but seems unlikely.

Yeah this rumour is pretty weird. If it were true what I’d expect is that Apple skip the M5 Pro/Max and update with M6 where the redesign is expected. But the Gurman tier of the rumour mill has already said there’s an M5 Pro/Max early next year *and* M6 redesign updates late next year or early 2027.

Someone is definitely wrong.
 
  • Like
Reactions: crazy dave
Yeah this rumour is pretty weird. If it were true what I’d expect is that Apple skip the M5 Pro/Max and update with M6 where the redesign is expected. But the Gurman tier of the rumour mill has already said there’s an M5 Pro/Max early next year *and* M6 redesign updates late next year or early 2027.

Someone is definitely wrong.
Apple could do what they did with the 2018 15" to 2019 16" MBP: drop the same Coffee Lake 9th gen, betting on a chassis redesign with various hardware upgrades is enough to sell.
 
Apple could do what they did with the 2018 15" to 2019 16" MBP: drop the same Coffee Lake 9th gen, betting on a chassis redesign with various hardware upgrades is enough to sell.

Yeah that’s my assumption as well. M2 and M3 happened same year too due to a similar situation as M5 so I could see it.
 
Or the base M5 is so powerful they put it in the old chassis. Meanwhile the delayed Pro and Maxes get the new good stuff with the new chassis and screens.

And it’ll be so good it will last a long time. Therefore only base M6 for MBP (and Airs etc) next time around.
 
Apple could do what they did with the 2018 15" to 2019 16" MBP: drop the same Coffee Lake 9th gen, betting on a chassis redesign with various hardware upgrades is enough to sell.
Aye they could do something like that but then you'd have the oddity that the M6 does in fact exist and would presumably be going into the 14". I guess right now we have M3 Ultra and M4 Maxes side by side in Studios but that does feel different, especially since the Ultra is such a low volume product and even for Intel/AMD workstation-class CPUs tend to take awhile to come to market as well.

Yeah that’s my assumption as well. M2 and M3 happened same year too due to a similar situation as M5 so I could see it.

Sure, but Apple did actually release the M3 Pro and Max in that year, here they're saying no M6 Pro/Max. Hmmm ...
 
What would be nice is if we get the pro/max/ultra released for mbp and studios at the same time. To me that seems like the setup now. And with the swirling rumors about new monitos as well all suggesting q1. Maybe we will get a an ”pro event” even?
extrapolation from the 1.6 inc in blender rendering gen to gen for the m5, Indicates that and ultra finally would be on par with nvidia high end, just one year later which is an impressive catching up. And LLM perf will have a massive boost , at least as big as on the base chips.
So, it is a matter of getting it released then. If they wait another year to release m5 ultra, they continue this awkward cadence that makes it feel like the ultras always is a bad choice.
 
Aye they could do something like that but then you'd have the oddity that the M6 does in fact exist and would presumably be going into the 14". I guess right now we have M3 Ultra and M4 Maxes side by side in Studios but that does feel different, especially since the Ultra is such a low volume product and even for Intel/AMD workstation-class CPUs tend to take awhile to come to market as well.



Sure, but Apple did actually release the M3 Pro and Max in that year, here they're saying no M6 Pro/Max. Hmmm ...
Screenshot 2025-10-16 at 15.58.34.png
Go to Apple.com right now, in the new MBP M5 page this image is almost at the top. They have no problem laying out generations of chips in the same lineup, if it creates confusion or not they roll with it.
 
View attachment 2568408
Go to Apple.com right now, in the new MBP M5 page this image is almost at the top. They have no problem laying out generations of chips in the same lineup, if it creates confusion or not they roll with it.
That's true, but also not expected to last very long - a few months at most while the M5 Pro/Maxes are readied (the reason why they need more time for the M5 Pro/Max itself might be interesting). In contrast, skipping the M6 Pro/Max would be for an entire generation. I'm not saying that there's 0 chance of this, I just find it unlikely. Like, what would the reason to skip the M6 Pro/Max in particular be? 2026 chips should be on TSMC's new 2nm node which should provide pretty big uplifts in terms of performance and power and density if reports are to be believed, not taking advantage of for the entire lineup seems odd. Then there's the rumored chassis and screen upgrades as well. Maybe Apple sees doing it all at once too much? After all it's rumored that chassis/screen issues delayed the M1 Pro/Max and new MBPs, but this would be the opposite? Will TSMC 2nm not have the volume to produce Pro/Max chips? Maybe. We know that Apple reused A16 chips for its regular iPhone 15 during the move to the N3B (again not saying 0 chance of this happening as Apple has, once, recycled chips), but that was a node with known delays and issues. I've heard nothing that says 2nm is having problems, if anything I think I heard it was ahead of schedule - checking online it seems to be at least on time.

What would be nice is if we get the pro/max/ultra released for mbp and studios at the same time. To me that seems like the setup now. And with the swirling rumors about new monitos as well all suggesting q1. Maybe we will get a an ”pro event” even?
extrapolation from the 1.6 inc in blender rendering gen to gen for the m5, Indicates that and ultra finally would be on par with nvidia high end, just one year later which is an impressive catching up. And LLM perf will have a massive boost , at least as big as on the base chips.
So, it is a matter of getting it released then. If they wait another year to release m5 ultra, they continue this awkward cadence that makes it feel like the ultras always is a bad choice.

Yeah that raises another good question, given what we're seeing in early benchmarks for the M5, how does Apple handle the Studio M3 Ultra with respect to the M5 Max? - especially if the M5 Ultra is delayed or only goes into the Mac Pro as some have suggested.

That said, workstation chips being released substantially behind their consumer counterparts is fairly common in the industry - e.g. Threadripper Zen 4/5 came out a year (more for Zen 4) after the first Zen 4/5 chips and Intel routinely takes a year/year and half for some of its equivalent chips after consumer chips have dropped. Of course some species of server chips are released simultaneously or near enough with their consumer counterparts. That Apple has had a nearly yearly release schedule for the last few generations of course makes a similar delay (on the long side admittedly) look worse for them.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.