M4 Mac Announcements

Small CBR24 efficiency update adding Intel Arrow Lake (285H) + M4 base (previously was an estimate) + another two HX370 points for comparison with Arrow Lake:

(expand chart)

Screenshot 2025-02-12 at 9.45.36 PM.png

Usual caveats from previous posts apply. With Arrow Lake analysis, NotebookCheck finally posted Apple M4 (base) results. My previous M4 base estimate was nearly spot-on for single thread, well within random variance. For multithreaded perf/efficiency, I was estimating efficiency based on a lower performing M4 chip that had a score of around 950 but 10% better efficiency than the M4 MacBook Pro Notebookcheck reported both performance and power for - possibly within random variation especially considering the lower performance. So not bad.

As NotebookCheck says 16-core Arrow Lake is an odd duck especially in relation to the existence of 8-core Lunar Lake. Of course Lunar Lake keeps going to lower power levels with lower performance, has a smaller CPU, and has much better single threaded efficiency (as an aside it also apparently has a better NPU and newer GPU). Although given how reportedly expensive Lunar Lake is with its on-package memory, it isn't clear if it is more cost-effective for Intel than Arrow Lake. But Lunar Lake's 8-core CPU clearly can't perform MT tasks very well. It's not designed to, but regardless Arrow Lake with its larger core count can easily blow past it in both performance and efficiency and can go down to the power levels that Lunar Lake operates at (though not the lowest possible levels for Lunar Lake).

So how does Arrow Lake compare to its competitors? Well the Apple M4 is so far ahead of just about everyone in single threaded performance/efficiency that it’s not really worth comparing. There were two Intel Arrow Lake devices with slightly different efficiencies and I chose the better of the two. This had an identical efficiency to the Strix Point chip albeit at a higher power draw/performance which is a small win (slightly better node plays a part here). The Qualcomm chips get similar performance but at much lower power.

In multithreaded efficiency, there are two Arrow Lake data points (~46W, MSI, and ~34W, Zenbook). This 16-core/thread Arrow Lake is very similar in performance and efficiency to the 12-core/24-thread HX 370 Strix Point chip at the higher power draw in the MSI device. This sort of tracks with expectations even though the Arrow Lake is on a slightly better node it has 14-16 threads - 2 are on a low power island (and don’t participate in multicore workloads making it effectively a 14-core), 6 are P-cores, and the remaining 8 are E-cores, while if I remember correctly the uplift from hyperthreading in CB R24 is roughly 25% making the HX 370 roughly a 15-thread equivalent (though all of those are effectively P-cores in the context of multithreading given that "c"-cores should behave similarly enough to P-cores here). But something clearly is wrong with the Arrow Lake Zenbook at the lower power draw getting only 740 points, it should be doing better. The Arrow Lake CPU has exact same efficiency here as at the higher power draw, which shouldn’t happen. At the lower power draw, with the same number of cores, its efficiency should increase as clock speeds go down. But it doesn’t. Not sure why. The Zenbook oddly had the better single threaded efficiency between the two, so it isn't like the Zenbook is just worse all around. The AMD HX 370 and Qualcomm X1E-78 show expected MT performance curves as power increases. The Arrow Lake H-series can also go to higher power levels, but it remains to be seen what performance gains that yields.*

Higher power/performance Arrow Lake HX-CPUs with 24-cores/thread are expected as are larger 16-core/32-thread Strix Halo and Fire range AMD CPUs. Based on results so far, even when these chips match the performance of the Apple M-series, it'll inevitably be at higher power draws even with the larger core/thread counts. These larger core/thread counts would in theory allow for greater down clocking and efficiencies to achieve the same performance, but relative to the M4, Apple's microarchitecture advantages means that still doesn't bring them to parity even in a test that is very multithreaded like CB R24. The closest these x86 processors get in MT efficiency to an Apple processor occurs at ~37W the HX 370 just misses the base M4's performance/efficiency, but the base M4 achieves this with significantly fewer threads available and only 4 P-cores. For any task that is single-threaded or lightly threaded, Apple's advantage grows. And when Apple adds P-cores for chips that are designed for greater multithreaded throughput, the efficiency of M4 Pro and Max becomes even tougher for AMD/Intel to match.

*EDIT: The MSI TDP chart in the Arrow Lake analysis article gives us some clue as to the Zenbook’s behavior. While NBC didn't measure wall power at each TDP, we can see that as power decreases performance for the Intel Arrow Lake H chip drops off significantly faster than for the AMD chip assuming they are drawing similar power at the same TDP, which they are definitely aren't given the wall power results. Even so, given the Zenbook results, this is not what I was expecting from the performance/power curve, so hopefully they add more wall power measurements for Arrow Lake H at different performance settings. It’s possible Artie Lake H just doesn’t do well at low power for some reason.
 
Last edited:
Yep. Same thing I found a while ago and updated (though I charted it but didn’t graph at the time). The CB24 wall data is pretty good Imho, not ideal but directionally good because we’re capturing enough information about the CPU through the chain (including PMIC stuff). The only gripe I have is that FP is not that important, but the thing is, it’s still modestly to strongly correlated with Integer performance and efficiency, so it’s directionally again a fine indicator.

And yeah one thing you’ll find is the QC stuff is like an intermediate point between Apple and X86 stuff generally. With the next one it should be not quite Apple but within the 10-25% type stuff on perf at a given wattage in ST or MT*, like on phones now

*MT is always easy to game though, like as you see with Intel/AMD one thing they love doing is comparing an MT result at the midpoint/optimal range of a bigger core’s efficiency and with *more* of them than Apple and comparing to an M chip at the peak of it’s range. Regardless it is true their disadvantage is less pronounced in MT though even if you tried to “equalize” and just compare a platform with similar total big cores throughout their curves and this is *partially* because of all the overhead that I’ve talked about here, which Lunar Lake fixed on power delivery & with cache but still only got them to about Qualcomm Gen 1 screwup tier efficiency —their architecture is just worse ofc.

The Arrow Lake result is funny because it says what I think most here would have for years now. Intel’s architecture is the big problem, not the fabs. The fabs make it all worse obviously, but like fabs (ok, broadly speaking within some variation) aren’t actually why Intel or AMD’s idle and low load power can’t compete with Apple, or why their IPC is lower & the performance curves in ST are so horizontal vs Apple (and Arm’s cores).
 
FWIW: there is other data with general benchmarks and software-modeled measurement that show Arrow Lake in a similar place, e.g. just okay.

Also lol



This isn’t true, functionally it isn’t bad that’s fair from a consumer POV but it’s an indictment of Intel because Arrow Lake is doing the “scale more cores” thing vs lunar lake at 18-35W, which, yeah that’s exactly the same thing as when Intel/AMD guys compared to M stuff.


It’s crazy how reflexively biased hardware communities are in favor of AMD and Intel. You almost invariably see comments quick to praise the most mediocre slop jobs as if it were an unthinkable achievement and competitive on its own grounds as a feat of engineering. Often for C+ to B- products comparing to Apple and Arm vendors or Nvidia
 
Yep. Same thing I found a while ago and updated (though I charted it but didn’t graph at the time). The CB24 wall data is pretty good Imho, not ideal but directionally good because we’re capturing enough information about the CPU through the chain (including PMIC stuff). The only gripe I have is that FP is not that important, but the thing is, it’s still modestly to strongly correlated with Integer performance and efficiency, so it’s directionally again a fine indicator.

And yeah one thing you’ll find is the QC stuff is like an intermediate point between Apple and X86 stuff generally. With the next one it should be not quite Apple but within the 10-25% type stuff on perf at a given wattage in ST or MT*, like on phones now

*MT is always easy to game though, like as you see with Intel/AMD one thing they love doing is comparing an MT result at the midpoint/optimal range of a bigger core’s efficiency and with *more* of them than Apple and comparing to an M chip at the peak of it’s range. Regardless it is true their disadvantage is less pronounced in MT though even if you tried to “equalize” and just compare a platform with similar total big cores throughout their curves and this is *partially* because of all the overhead that I’ve talked about here, which Lunar Lake fixed on power delivery & with cache but still only got them to about Qualcomm Gen 1 screwup tier efficiency —their architecture is just worse ofc.

The Arrow Lake result is funny because it says what I think most here would have for years now. Intel’s architecture is the big problem, not the fabs. The fabs make it all worse obviously, but like fabs (ok, broadly speaking within some variation) aren’t actually why Intel or AMD’s idle and low load power can’t compete with Apple, or why their IPC is lower & the performance curves in ST are so horizontal vs Apple (and Arm’s cores).
Unlike NotebookCheck, I choose to subtract out idle power to make my graphs, which does give a lot of AMD/Intel systems a boost relative to Apple/QC. Not all of the x86 devices have poor idle power but they are definitely more likely to. One of the main reasons I subtract it out though is that I feel it’s unfair to include when measuring CPU efficiency if the device has poor idle power because of a dGPU (e.g. the AMD graphed device with a HX 370, the Pro Art 16, has a 4070 mobile and an idle power of 10.2W, but other HX 370 devices without dGPUs have lower idle power like the HX 370 Zenbook 16" with 6.4W). Also different devices with the same chip can have different idle power, sometimes just random variance or OEM differences and often just bigger devices have higher idle power (e.g. the 16" MacBook Pro M4 Pro uses 5.98W while the 14" Pro uses 2.62W). So I often find subtracting idle from load makes the results more sane (though not always admittedly) and I figure this way it’s as close to being able to measure package power physically as we’re going to get. It also doesn't completely remove the effects of larger chips as you can see in the single threaded results from comparing M4 to M4 Pro to M4 Max and Lunar Lake to Arrow Lake (obviously more going on with the latter, but still).

So yes x86 chips often get a benefit from it, but that means whenever you look at my graphs, any advantages you see for Apple/QC are in addition to any advantages in idle power.

I would love if NotebookCheck (or someone else) also did standardized, cross platform integer efficiency analysis. Benchmarking, say, compilation would be a fairly straightforward as you could just as easily loop it to run for X minutes a la CB R24 and do it for single and multicore (and everything in between, i.e. n-core which CB R24 allows). Heck there are several such benchmarks for compilation out there already. Just ... no one pairs that with reporting wall power (or even software-based power measurements) on a very regular basis. But that would be very, very cool. Especially to have both! Obviously there would still be lots of other integer/floating point algorithms with their own characteristics stressing different parts of the CPU, but still having compilation and rendering would cover a lot. (also having something less parallel but still multicore like GB does would be nice - you could fake it with "n-core" style multicore benchmarks, but a benchmark that actually requires inter-thread communication as opposed to spawning multiple independent processes that only communicate upon termination would be cool)

NotebookCheck has been doing Wall Power vs FPS for The Witcher 3 and CP 2077 (FHD ultra), but I haven't made the above graphs because they aren't native either for Macs (or I think even Windows on Arm? is it?). Obviously I could still do it for just x86 machines, but that's not really my focus or I could just do it anyways with the non-native caveat (as NBC does). However, CP 2077 is coming to the Mac natively soon so I may start, although unfortunately I think most of the CP 2077 efficiency data is from an older build as I noticed the efficiency results for "CP 2077" doesn't match the FPS from "CP 2077 Phantom Liberty 2.1". So I don't know how much comparative data NBC will be able to report. That said, still looking forward to it. Again, if/when I do gaming efficiency graphs, I'll probably still subtract idle power even though that will give a substantial benefit to those devices with dGPUs.
 
Last edited:
FWIW: there is other data with general benchmarks and software-modeled measurement that show Arrow Lake in a similar place, e.g. just okay.

Also lol



This isn’t true, functionally it isn’t bad that’s fair from a consumer POV but it’s an indictment of Intel because Arrow Lake is doing the “scale more cores” thing vs lunar lake at 18-35W, which, yeah that’s exactly the same thing as when Intel/AMD guys compared to M stuff.


It’s crazy how reflexively biased hardware communities are in favor of AMD and Intel. You almost invariably see comments quick to praise the most mediocre slop jobs as if it were an unthinkable achievement and competitive on its own grounds as a feat of engineering. Often for C+ to B- products comparing to Apple and Arm vendors or Nvidia


Yeah, for a lot of multicore benchmarks just adding cores is an easy way to get wins, which is why I agree with Geekbench's approach with version 6 in general to dissuade GB top level scores from being used in MOAR CORES marketing when not everyone benefits from that (while still reporting the cases in subtests where indeed more cores is a win). Also from that reddit thread: "When you are an engineer. you ALWAYS need the good old x86" ... hmmmm ... funnily enough from that thread talking about running old proprietary software there have been occasions (older games) where I've had better luck with WINE than Windows Compatibility mode.
 
New analysis post in the Strix Halo thread comparing the Halo and M4 (sadly only one Halo data point so far, but still some things we can say about it):

 
Can anyone refresh my memory as to the missing M4 Mac model numbers? I ask as Mac16,12 has just appeared on Geekbench’s Metal db.
View attachment 33936
@Altaic's list M4 which he got from diving into firmware which has been confirmed for all but one device (16,9 still unconfirmed but with Macrumors agreeing that 16,12 and 16,13 are the Airs and given recent GB postings seems pretty locked in) at this point:

M4 Macs
Mac16,1 MBP 14” M4
Mac16,2 iMac 24” M4 (2-port)
Mac16,3 iMac 24” M4 (4-port)
Mac16,4 DNE
Mac16,5 MBP 16” M4 Max (384b & 512b)
Mac16,6 MBP 14” M4 Max (384b & 512b)
Mac16,7 MBP 16” M4 Pro
Mac16,8 MBP 14” M4 Pro
Mac16,9 Mac Studio M4 Max (last unconfirmed device)
Mac16,10 Mac mini M4
Mac16,11 Mac mini M4 Pro
Mac16,12 MBA 13” M4
Mac16,13 MBA 15” M4

Any 16,14 or 16,15 device (i.e. M4 Ultra Studio and M4 Ultra Pro) is either not coming or not coming until after 17,1 & 17,2 which are coming before the next OS since they are already listed and 16,14 and 16,15 are simply coming after the next OS release in the fall. Possible but I feel unlikely which is why I favor that 17,1 and 17,2 are the next Studio and Pro.
 
Last edited:
@Altaic's list M4 which he got from diving into firmware which has been confirmed for all but one device (16,9 still unconfirmed but with Macrumors agreeing that 16,12 and 16,13 are the Airs and given recent GB postings seems pretty locked in) at this point:

M4 Macs
Mac16,1 MBP 14” M4
Mac16,2 iMac 24” M4 (2-port)
Mac16,3 iMac 24” M4 (4-port)
Mac16,4 DNE
Mac16,5 MBP 16” M4 Max (384b & 512b)
Mac16,6 MBP 14” M4 Max (384b & 512b)
Mac16,7 MBP 16” M4 Pro
Mac16,8 MBP 14” M4 Pro
Mac16,9 Mac Studio M4 Max (last unconfirmed device)
Mac16,10 Mac mini M4
Mac16,11 Mac mini M4 Pro
Mac16,12 MBA 13” M4
Mac16,13 MBA 15” M4

Any 16,14 or 16,15 device (i.e. M4 Ultra Studio and M4 Ultra Pro) is either not coming or not coming until after 17,1 & 17,2 which are coming before the next OS since they are already listed and 16,14 and 16,15 are simply coming after the next OS release in the fall. Possible but I feel unlikely which is why I favor that 17,1 and 17,2 are the next Studio and Pro.
Many thanks. So am I understanding you in saying the upcoming Studio will be an M5 in your opinion?
 
Many thanks. So am I understanding you in saying the upcoming Studio will be an M5 in your opinion?
At least M4.5 or something new like a “P1”. Something that makes it a new device generation and not just a different model number. But it could just be odd timing where M5s are coming before the final M4s and the new OS is releasing in between. Die shots of M4 Max would be helpful.
 
My wife wants a new air (she has an M1) to keep her work documents segregated from her home documents, just in case, and the timing looks good.
 
Many thanks. So am I understanding you in saying the upcoming Studio will be an M5 in your opinion?

At least M4.5 or something new like a “P1”. Something that makes it a new device generation and not just a different model number. But it could just be odd timing where M5s are coming before the final M4s and the new OS is releasing in between. Die shots of M4 Max would be helpful.
I should also specify, the M4 Max can be used in the next Studio, in fact that is likely to be the last unconfirmed 16,9 device. It’s specifically the Ultra-level Studio/Pro devices that are currently up in the air.
 
Hi, everyone. I created an account to give my $0.02 on the M4 identifiers and the mystery surrounding the M4 Ultra. My original source for the list is this now famous post at The Other Place™. I have modified the list below (in bold) to reflect what we now know about the released M4s, the soon-to-be-released M4 MBAs, and what can only be the plain vanilla M4 Max Mac Studio.

M4 (projected)

Mac16,1 :: M4 120 (8/8) iMac (Two ports)
Mac16,2 :: M4 120 (10/10) iMac (Four ports)
Mac16,3 :: M4 120 (10/10) MacBook Pro 14"
Mac16,5 :: M4 Pro MacBook Pro 14
Mac16,7 :: M4 Max MacBook Pro 14"
Mac16,6 :: M4 Pro MacBook Pro 16"
Mac16,8 :: M4 Max MacBook Pro 16"
Mac16,9 :: M4 Max Mac Studio
Mac16,10 :: M4 120 (10/10) Mac mini
Mac16,11 :: M4 Pro Mac mini
Mac16,12 :: M4 MacBook Air 13"
Mac16,13 :: M4 MacBook Air 15"

M5
(projected)

Mac17,1 :: M4 Ultra Mac Studio
Mac17,2 :: M4 Ultra Mac Pro



The Mac17,1 and Mac17,2 identifiers were originally thought to be M5s, launching first in the MacBook Air, but now that M4 MBAs are all but confirmed as Mac16,12 and Mac16,13, I think they are the M4 Ultra Mac Studio and M4 Ultra Mac Pro.

But wait, you say, the 17 identifiers can't be M4s, they all use the 16 prefix. 17=M5. Normally I would agree, but the other circle we have to square is Gurman's famous Hidra chip. As its two-headed code name implies, it was long thought to be two M4 Maxes joined via UltraFusion to make an M4 Ultra (just like the M1 and M2 Ultras), but the M4 identifier list no longer allows for that.

So what if one head is a full-reticle CPU, and the other is a full-reticle GPU, and those two halves are joined by a (next-gen) UltraFusion into a massive effective SoC with the same shared memory as other M-series chips. And with binning on both or either of the CPU/GPU sides, Apple could great multiple variants of the Ultra chip for those that want more CPU than GPU, vice versa, or full cores on both sides.

Such a chip would more than warrant the internal move to the 17 prefix to distinguish it from the "normal" 16-prefix M4s, yet Apple could still choose to brand it as a member of the M4 family for marketing purposes and continuity. They want this Ultra to be the last of the M4s, not the first of the M5s.

I say we get this "M4+" Hidra Chiplet monster in the Mac Studio (alongside a plain vanilla M4 Max Mac Studio), and in the Mac Pro at WWDC. Throw in a refreshed 32" Pro Display XDR with TB5, 120Hz ProMotion and thousands more dimming zones and you've got quite an event.
 
Hi, everyone. I created an account to give my $0.02 on the M4 identifiers and the mystery surrounding the M4 Ultra. My original source for the list is this now famous post at The Other Place™. I have modified the list below (in bold) to reflect what we now know about the released M4s, the soon-to-be-released M4 MBAs, and what can only be the plain vanilla M4 Max Mac Studio.

M4 (projected)

Mac16,1 :: M4 120 (8/8) iMac (Two ports)
Mac16,2 :: M4 120 (10/10) iMac (Four ports)
Mac16,3 :: M4 120 (10/10) MacBook Pro 14"
Mac16,5 :: M4 Pro MacBook Pro 14
Mac16,7 :: M4 Max MacBook Pro 14"
Mac16,6 :: M4 Pro MacBook Pro 16"
Mac16,8 :: M4 Max MacBook Pro 16"
Mac16,9 :: M4 Max Mac Studio
Mac16,10 :: M4 120 (10/10) Mac mini
Mac16,11 :: M4 Pro Mac mini
Mac16,12 :: M4 MacBook Air 13"
Mac16,13 :: M4 MacBook Air 15"

M5
(projected)

Mac17,1 :: M4 Ultra Mac Studio
Mac17,2 :: M4 Ultra Mac Pro



The Mac17,1 and Mac17,2 identifiers were originally thought to be M5s, launching first in the MacBook Air, but now that M4 MBAs are all but confirmed as Mac16,12 and Mac16,13, I think they are the M4 Ultra Mac Studio and M4 Ultra Mac Pro.

But wait, you say, the 17 identifiers can't be M4s, they all use the 16 prefix. 17=M5. Normally I would agree, but the other circle we have to square is Gurman's famous Hidra chip. As its two-headed code name implies, it was long thought to be two M4 Maxes joined via UltraFusion to make an M4 Ultra (just like the M1 and M2 Ultras), but the M4 identifier list no longer allows for that.

So what if one head is a full-reticle CPU, and the other is a full-reticle GPU, and those two halves are joined by a (next-gen) UltraFusion into a massive effective SoC with the same shared memory as other M-series chips. And with binning on both or either of the CPU/GPU sides, Apple could great multiple variants of the Ultra chip for those that want more CPU than GPU, vice versa, or full cores on both sides.

Such a chip would more than warrant the internal move to the 17 prefix to distinguish it from the "normal" 16-prefix M4s, yet Apple could still choose to brand it as a member of the M4 family for marketing purposes and continuity. They want this Ultra to be the last of the M4s, not the first of the M5s.

I say we get this "M4+" Hidra Chiplet monster in the Mac Studio (alongside a plain vanilla M4 Max Mac Studio), and in the Mac Pro at WWDC. Throw in a refreshed 32" Pro Display XDR with TB5, 120Hz ProMotion and thousands more dimming zones and you've got quite an event.
Welcome!
 
Hi, everyone. I created an account to give my $0.02 on the M4 identifiers and the mystery surrounding the M4 Ultra. My original source for the list is this now famous post at The Other Place™. I have modified the list below (in bold) to reflect what we now know about the released M4s, the soon-to-be-released M4 MBAs, and what can only be the plain vanilla M4 Max Mac Studio.

M4 (projected)

Mac16,1 :: M4 120 (8/8) iMac (Two ports)
Mac16,2 :: M4 120 (10/10) iMac (Four ports)
Mac16,3 :: M4 120 (10/10) MacBook Pro 14"
Mac16,5 :: M4 Pro MacBook Pro 14
Mac16,7 :: M4 Max MacBook Pro 14"
Mac16,6 :: M4 Pro MacBook Pro 16"
Mac16,8 :: M4 Max MacBook Pro 16"
Mac16,9 :: M4 Max Mac Studio
Mac16,10 :: M4 120 (10/10) Mac mini
Mac16,11 :: M4 Pro Mac mini
Mac16,12 :: M4 MacBook Air 13"
Mac16,13 :: M4 MacBook Air 15"

M5
(projected)

Mac17,1 :: M4 Ultra Mac Studio
Mac17,2 :: M4 Ultra Mac Pro



The Mac17,1 and Mac17,2 identifiers were originally thought to be M5s, launching first in the MacBook Air, but now that M4 MBAs are all but confirmed as Mac16,12 and Mac16,13, I think they are the M4 Ultra Mac Studio and M4 Ultra Mac Pro.

But wait, you say, the 17 identifiers can't be M4s, they all use the 16 prefix. 17=M5. Normally I would agree, but the other circle we have to square is Gurman's famous Hidra chip. As its two-headed code name implies, it was long thought to be two M4 Maxes joined via UltraFusion to make an M4 Ultra (just like the M1 and M2 Ultras), but the M4 identifier list no longer allows for that.

So what if one head is a full-reticle CPU, and the other is a full-reticle GPU, and those two halves are joined by a (next-gen) UltraFusion into a massive effective SoC with the same shared memory as other M-series chips. And with binning on both or either of the CPU/GPU sides, Apple could great multiple variants of the Ultra chip for those that want more CPU than GPU, vice versa, or full cores on both sides.

Such a chip would more than warrant the internal move to the 17 prefix to distinguish it from the "normal" 16-prefix M4s, yet Apple could still choose to brand it as a member of the M4 family for marketing purposes and continuity. They want this Ultra to be the last of the M4s, not the first of the M5s.

I say we get this "M4+" Hidra Chiplet monster in the Mac Studio (alongside a plain vanilla M4 Max Mac Studio), and in the Mac Pro at WWDC. Throw in a refreshed 32" Pro Display XDR with TB5, 120Hz ProMotion and thousands more dimming zones and you've got quite an event.
Do you have an account at the other place too?

Are you tenthousandthings?
 
So what if one head is a full-reticle CPU, and the other is a full-reticle GPU, and those two halves are joined by a (next-gen) UltraFusion into a massive effective SoC with the same shared memory as other M-series chips. And with binning on both or either of the CPU/GPU sides, Apple could great multiple variants of the Ultra chip for those that want more CPU than GPU, vice versa, or full cores on both sides.

I say we get this "M4+" Hidra Chiplet monster in the Mac Studio (alongside a plain vanilla M4 Max Mac Studio), and in the Mac Pro at WWDC. Throw in a refreshed 32" Pro Display XDR with TB5, 120Hz ProMotion and thousands more dimming zones and you've got quite an event.

WWDC 2025 will introduce the all-new Mac Pro Cube featuring the M4+ Hidra...! ;^p
 
Back
Top