The 2020 Mac Mini Unleashed: Putting Apple Silicon M1 To The Testby Andrei Frumusanu on November 17, 2020 9:00 AM EST
Last week, Apple made industry news by announcing new Mac products based upon the company’s new Apple Silicon M1 SoC chip, marking the first move of a planned 2-year roadmap to transition over from Intel-based x86 CPUs to the company’s own in-house designed microprocessors running on the Arm instruction set.
During the launch we had prepared an extensive article based on the company’s already related Apple A14 chip, found in the new generation iPhone 12 phones. This includes a rather extensive microarchitectural deep-dive into Apple’s new Firestorm cores which power both the A14 as well as the new Apple Silicon M1, I would recommend a read if you haven’t had the opportunity yet:
Since a few days, we’ve been able to get our hands on one of the first Apple Silicon M1 devices: the new Mac mini 2020 edition. While in our analysis article last week we had based our numbers on the A14, this time around we’ve measured the real performance on the actual new higher-power design. We haven’t had much time, but we’ll be bringing you the key datapoints relevant to the new Apple Silicon M1.
Apple Silicon M1: Firestorm cores at 3.2GHz & ~20-24W TDP?
During the launch event, one thing that was in Apple fashion typically missing from the presentation were actual details on the clock frequencies of the design, as well as its TDP which it can sustain at maximum performance.
We can confirm that in single-threaded workloads, Apple’s Firestorm cores now clock in at 3.2GHz, a 6.66% increase over the 3GHz frequency of the Apple A14. As long as there's thermal headroom, this clock also applies to all-core loads, with in addition to 4x 3.2GHz performance cores also seeing 4x Thunder efficiency cores at 2064MHz, also quite a lot higher than 1823MHz on the A14.
Alongside the four performance Firestorm cores, the M1 also includes four Icestorm cores which are aimed for low idle power and increased power efficiency for battery-powered operation. Both the 4 performance cores and 4 efficiency cores can be active in tandem, meaning that this is an 8-core SoC, although performance throughput across all the cores isn’t identical.
The biggest question during the announcement event was the power consumption of these designs. Apple had presented several charts including performance and power axes, however we lacked comparison data as to come to any proper conclusion.
As we had access to the Mac mini rather than a Macbook, it meant that power measurement was rather simple on the device as we can just hook up a meter to the AC input of the device. It’s to be noted with a huge disclaimer that because we are measuring AC wall power here, the power figures aren’t directly comparable to that of battery-powered devices, as the Mac mini’s power supply will incur a efficiency loss greater than that of other mobile SoCs, as well as TDP figures contemporary vendors such as Intel or AMD publish.
It’s especially important to keep in mind that the figure of what we usually recall as TDP in processors is actually only a subset of the figures presented here, as beyond just the SoC we’re also measuring DRAM and voltage regulation overhead, something which is not included in TDP figures nor your typical package power readout on a laptop.
Starting off with an idle Mac mini in its default state while sitting idle when powered on, while connected via HDMI to a 2560p144 monitor, Wi-Fi 6 and a mouse and keyboard, we’re seeing total device power at 4.2W. Given that we’re measuring AC power into the device which can be quite inefficient at low loads, this makes quite a lot of sense and represents an excellent figure.
This idle figure also serves as a baseline for following measurements where we calculate “active power”, meaning our usual methodology of taking total power measured and subtracting the idle power.
During average single-threaded workloads on the 3.2GHz Firestorm cores, such as GCC code compilation, we’re seeing device power go up to 10.5W with active power at around 6.3W. The active power figure is very much in line with what we would expect from a higher-clocked Firestorm core, and is extremely promising for Apple and the M1.
In workloads which are more DRAM heavy and thus incur a larger power penalty on the LPDDR4X-class 128-bit 16GB of DRAM on the Mac mini, we’re seeing active power go up to 10.5W. Already with these figures the new M1 is might impressive and showcases less than a third of the power of a high-end Intel mobile CPU.
In multi-threaded scenarios, power highly depends on the workload. In memory-heavy workloads where the CPU utilisation isn’t as high, we’re seeing 18W active power, going up to around 22W in average workloads, and peaking around 27W in compute heavy workloads. These figures are generally what you’d like to compare to “TDPs” of other platforms, although again to get an apples-to-apples comparison you’d need to further subtract some of the overhead as measured on the Mac mini here – my best guess would be a 20 to 24W range.
Finally, on the part of the GPU, we’re seeing a lower power consumption figure of 17.3W in GFXBench Aztec High. This would contain a larger amount of DRAM power, so the power consumption of Apple’s GPU is definitely extremely low-power, and far less than the peak power that the CPUs can draw.
Besides the additional cores on the part of the CPUs and GPU, one main performance factor of the M1 that differs from the A14 is the fact that’s it’s running on a 128-bit memory bus rather than the mobile 64-bit bus. Across 8x 16-bit memory channels and at LPDDR4X-4266-class memory, this means the M1 hits a peak of 68.25GB/s memory bandwidth.
In terms of memory latency, we’re seeing a (rather expected) reduction compared to the A14, measuring 96ns at 128MB full random test depth, compared to 102ns on the A14.
Of further note is the 12MB L2 cache of the performance cores, although here it seems that Apple continues to do some partitioning as to how much as single core can use as we’re still seeing some latency uptick after 8MB.
The M1 also contains a large SLC cache which should be accessible by all IP blocks on the chip. We’re not exactly certain, but the test results do behave a lot like on the A14 and thus we assume this is a similar 16MB chunk of cache on the SoC, as some access patterns extend beyond that of the A14, which makes sense given the larger L2.
One aspect we’ve never really had the opportunity to test is exactly how good Apple’s cores are in terms of memory bandwidth. Inside of the M1, the results are ground-breaking: A single Firestorm achieves memory reads up to around 58GB/s, with memory writes coming in at 33-36GB/s. Most importantly, memory copies land in at 60 to 62GB/s depending if you’re using scalar or vector instructions. The fact that a single Firestorm core can almost saturate the memory controllers is astounding and something we’ve never seen in a design before.
Because one core is able to make use of almost the whole memory bandwidth, having multiple cores access things at the same time don’t actually increase the system bandwidth, but actually due to congestion lower the effective achieved aggregate bandwidth. Nevertheless, this 59GB/s peak bandwidth of one core is essentially also the speed at which memory copies happen, no matter the amount of active cores in the system, again, a great feat for Apple.
Beyond the clock speed increase, L2 increase, this memory boost is also very likely to help the M1 differentiate its performance beyond that of the A14, and offer up though competition against the x86 incumbents.
- Page 1: Apple Silicon M1: Recap, Power Consumption
- Page 2: Benchmarks: Whatever Is Available
- Page 3: M1 GPU Performance: Integrated King, Discrete Rival
- Page 4: SPEC2006 & 2017: Industry Standard - ST Performance
- Page 5: SPEC2017 - Multi-Core Performance
- Page 6: Rosetta2: x86-64 Translation Performance
- Page 7: Conclusion & First Impressions
Post Your CommentPlease log in or sign up to comment.
View All Comments
Eric S - Tuesday, November 17, 2020 - linkThat cash is the reason Apple is getting so much of the 5 nm node production.
varase - Wednesday, November 25, 2020 - linkYou can pretty much forget Microsoft - there is no compelling ARM Microsoft software, and if ARM Windows does do x86 transcompiling it will almost certain be to the standard ARM instruction set, or worse to a Microsoft/Qualcomm mutated instruction set. In no case would it be the Apple SIlicon's AArch64 implantation.
If they relied on interpretation instead of trans compilation, expect performance to be less than stellar.
Now Parallels seems to be working on something that they're keeping pretty mum about - my guess would be a hypervisor running x64 clients. Using Rosetta 2 like trans compilation, they could front end OS boot and segment loaders and read x64 code segments and return Apple Silicon AArch64 code to the client virtual machine. They'd probably have to front end code signing segments if those exist. To sustain performance, they'd also have to cache transcompiled code using a source/CRC/length key to prevent having to transcompile all the code all the time.
They wouldn't have Metal access to GPUs to lean back on, so unless Apple implements PCIe attached graphic cards I wouldn't expect gaming to ever be performant enough to be practical.
hlovatt - Tuesday, November 17, 2020 - linkIsn't the 22 W you quote for Apple for the whole system, whereas the 25 W you quote for AMD is just the processor? In't a 10 W Apple processor competitive with a 25 W AMD processor?
halo37253 - Wednesday, November 18, 2020 - linkNo thats full system power from the wall of AMD's 4800u in 15watt mode.
whatthe123 - Tuesday, November 17, 2020 - linkBy anandtech's standards these benchmarks are highly misleading, though. 5950x is capped off to its lowest possible package power. In MT testing they switch back to zen 2 chips also power limited. Everything is focusing on efficiency, which is admittedly very, very good, but the article frames it as though these are stock comparisons, when in reality most of these CPUs would be able to draw more power and dwarf the M1 in performance.
If they are only looking at efficiency, why make such a misleading article? Just focus on efficiency and the results are stellar. Instead they went with this mess of an article, I'm honestly shocked considering this site normally tries to be unbiased as possible.
Spunjji - Thursday, November 19, 2020 - link@whatthe123 - "5950x is capped off to its lowest possible package power" - where did you get that impression from?
Spunjji - Thursday, November 19, 2020 - link@whatthe123 - Regarding your complaint that they only compare the 5950X to the M1 in ST testing, of course they do, it's a 16-core 32-thread chip with a 105W TDP and ~140W power limit. It'll demolish the ~24W 4+4 M1 in MT. That's just... not a useful comparison.
The point is to show AMD's peak Zen 3 performance against Apple's peak Firestorm performance. Once AMD have Zen 3 processors in the ~25W range, then a valid MT comparison in comparable designs can be made.
helpmeoutnow - Thursday, November 26, 2020 - link@Spunjji but be fair we want to see the difference between this M1 and fully utilized 5950X just to see the real difference. Now it looks like m1 is a good cpu. but as it is said, they just cap everything else.
Stephen_L - Tuesday, November 17, 2020 - linkNah, no just listen to op, we HAVE to compare chips on the same node! Let’s wait for Intel 7nm also, hopefully in 2022 but god knows if they can do it before 2024, so we can have “Apples to apples comparison”. Let’s come back in 2-4 years guys. /s
magreen - Tuesday, November 24, 2020 - linkTotally agree. The Cyrix M3 Jalapeno when it comes out on 5nm is going to crush this little M1.