Section by Ryan Smith

M1 GPU Performance: Integrated King, Discrete Rival

While the bulk of the focus from the switch to Apple’s chips is on the CPU cores, and for good reason – changing the underlying CPU architecture if your computers is no trivial matter – the GPU aspects of the M1 are not to be ignored. Like their CPU cores, Apple has been developing their own GPU technology for a number of years now, and with the shift to Apple Silicon, those GPU designs are coming to the Mac for the very first time. And from a performance standpoint, it’s arguably an even bigger deal than Apple’s CPU.

Apple, of course, has long held a reputation for demanding better GPU performance than the average PC OEM. Whereas many of Intel’s partners were happy to ship systems with Intel UHD graphics and other baseline solutions even in some of their 15-inch laptops, Apple opted to ship a discrete GPU in their 15-inch MacBook Pro. And when they couldn’t fit a dGPU in the 13-inch model, they instead used Intel’s premium Iris GPU configurations with larger GPUs and an on-chip eDRAM cache, becoming one of the only regular customers for those more powerful chips.

So it’s been clear for some time now that Apple has long-wanted better GPU performance than what Intel offers by default. By switching to their own silicon, Apple finally gets to put their money where their mouth is, so to speak, by building a laptop SoC with all the GPU performance they’ve ever wanted.

Meanwhile, unlike the CPU side of this transition to Apple Silicon, the higher-level nature of graphics programming means that Apple isn’t nearly as reliant on devs to immediately prepare universal applications to take advantage of Apple’s GPU. To be sure, native CPU code is still going to produce better results since a workload that’s purely GPU-limited is almost unheard of, but the fact that existing Metal (and even OpenGL) code can be run on top of Apple’s GPU today means that it immediately benefits all games and other GPU-bound workloads.

As for the M1 SoC’s GPU, unsurprisingly it looks a lot like the GPU from the A14. Apple will have needed to tweak their design a bit to account for Mac sensibilities (e.g. various GPU texture and surface formats), but by and large the difference is abstracted away at the API level. Overall, with M1 being A14-but-bigger, Apple has scaled up their 4 core GPU design from that SoC to 8 cores for the M1. Unfortunately we have even less insight into GPU clockspeeds than we do CPU clockspeeds, so it’s not clear if Apple has increased those at all; but I would be a bit surprised if the GPU clocks haven’t at least gone up a small amount. Overall, A14’s 4 core GPU design was already quite potent by smartphone standards, so an 8 core design is even more so. M1’s integrated GPU isn’t just designed to outpace AMD and Intel’s integrated GPUs, but it’s designed to chase after discrete GPUs as well.

A Educated Guess At Apple GPU Specifications
  M1
ALUs 1024
(128 EUs/8 Cores)
Texture Units 64
ROPs 32
Peak Clock 1278MHz
Throughput (FP32) 2.6 TFLOPS
Memory Clock LPDDR4X-4266
Memory Bus Width 128-bit
(IMC)

Finally, it should be noted that Apple is shipping two different GPU configurations for the M1. The Mac Mini and MacBook Pro get chips with all 8 GPU cores enabled. Meanwhile for the Macbook Air, it depends on the SKU: the entry-level model gets a 7-core configuration, while the higher-tier model gets 8 cores. This means the entry-level Air gets the weakest GPU on paper – trailing a full M1 by around 12% – but it will be interesting to see how the shut-off core influences thermal throttling on that passively-cooled laptop.

Kicking off our look at GPU performance, let’s start with GFXBench 5.0. This is one of our regular benchmarks for laptop reviews as well, so it gives us a good opportunity to compare the M1-based Mac Mini to a variety of other CPU/GPU combinations inside and outside the Mac ecosystem. Overall this isn’t an entirely fair test since the Mac Mini is a small desktop rather than a laptop, but as M1 is a laptop-focused chip, this at least gives us an idea of how M1 performs when it gets to put its best foot forward.

GFXBench 5.0 Aztec Ruins Normal 1080p Offscreen

GFXBench 5.0 Aztec Ruins High 1440p Offscreen

Overall, the M1’s GPU starts off very strong here. At both Normal and High settings it’s well ahead of any other integrated GPU, and even a discrete Radeon RX 560X. Only once we get to NVIDIA’s GTX 1650 and better does the M1 finally run out of gas.

The difference compared to the 2018 Intel Mac Mini is especially night-and-day. The Intel UHD graphics (Gen 9.5) GPU in that system is vastly outclassed to the point of near-absurdity, delivering a performance gain over 6x. And even other configurations such as the 13-inch MBP with Iris graphics, or a PC with a Ryzen 4700U (Vega 7 graphics) are all handily surpassed. In short, the M1 in the new Mac Mini is delivering discrete GPU-levels of performance.

As an aside, I also took the liberty of running the x86 version of the benchmark through Rosetta, in order to take a look at the performance penalty. In GFXBench Aztec Ruins, at least, there is none. GPU performance is all but identical with both the native binary and with binary translation.

Futuremark 3DMark Ice Storm Unlimited - Graphics

Taking one last quick look at the wider field with an utterly silly synthetic benchmark, we have 3DMark Ice Storm Unlimited. Thanks to the ability for Apple Silicon Macs to run iPhone/iPad applications, we’re able to run this benchmark on a Mac for the first time by running the iOS version. This is a very old benchmark, built for the OpenGL ES 2.0 era, but it’s interesting that it fares even better than GFXBench. The Mac Mini performs just well enough to slide past a GTX 1650 equipped laptop here, and while this won’t be a regular occurrence, it goes to show just how potent M1 can be.

BaseMark GPU 1.2.1 - Medium

BaseMark GPU 1.2.1 - High

Another GPU benchmark that’s been updated for the launch of Apple’s new Macs is BaseMark GPU. This isn’t a regular benchmark for us, so we don’t have scores for other, non-Mac laptops on hand, but it gives us another look at how M1 compares to other Mac GPU offerings. The 2020 Mac Mini still leaves the 2018 Intel-based Mac Mini in the dust, and for that matter it’s at least 50% faster than the 2017 MacBook Pro with a Radeon Pro 560 as well. Newer MacBook Pros will do better, of course, but keep in mind that this is an integrated GPU with the entire chip drawing less power than just a MacBook Pro’s CPU, never mind the discrete GPU.

Rise of the Tomb Raider - Value

Rise of the Tomb Raider - Enthusiast

Finally, putting theory to practice, we have Rise of the Tomb Raider. Released in 2016, this game has a proper Mac port and a built-in benchmark, allowing us to look at the M1 in a gaming scenario and compare it to some other Windows laptops. This game is admittedly slightly older, but its performance requirements are a good match for the kind of performance the M1 is designed to offer. Finally, it should be noted that this is an x86 game – it hasn’t been ported over to Arm – so the CPU side of the game is running through Rosetta.

At our 768p Value settings, the Mac Mini is delivering well over 60fps here. Once again it’s vastly ahead of the 2018 Intel-based Mac Mini, as well as every other integrated GPU in this stack. Even the 15-inch MBP and its Radeon Pro 560 are still trailing the Mac Mini by over 25%, and it takes a Ryzen laptop with a Radeon 560X to finally pull even with the Mac Mini.

Meanwhile cranking things up to 1080p with Enthusiast settings finds that the M1-based Mac Mini is still delivering just shy of 40fps, and it’s now over 20% ahead of the aforementioned Ryzen + 560X system. This does leave the Mini well behind the GTX 1650 here – with Rosetta and general API inefficiencies likely playing a part – but it goes to show what it takes to beat Apple’s integrated GPU. At 39.6fps, the Mac Mini is quite playable at 1080p with good image quality settings, and it would be fairly easy to knock down either the resolution or image quality a bit to get that back above 60fps. All on an integrated GPU.

Update 11-17, 7pm: Since the publication of this article, we've been able to get access to the necessary tools to measure the power consumption of Apple's SoC at the package and core level. So I've gone back and captured power data for GFXBench Aztec Ruins at High, and Rise of the Tomb Raider at Enthusiast settings.

Power Consumption - Mac Mini 2020 (M1)
  Rise of the Tomb Raider (Enthusiast) GFXBench Aztec
(High)
Package Power 16.5 Watts 11.5 Watts
GPU Power 7 Watts 10 Watts
CPU Power 7.5 Watts 0.16 Watts
DRAM Power 1.5 Watts 0.75 Watts

The two workloads are significantly different in what they're doing under the hood. Aztec is a synthetic test that's run offscreen in order to be as pure of a GPU test as possible. As a result it records the highest GPU power consumption – 10 Watts – but it also barely scratches the CPU cores virtually untouched (and for that matter other elements like the display controlller). Meanwhile Rise of the Tomb Raider is a workload from an actual game, and we can see that it's giving the entire SoC a workout. GPU power consumption hovers around 7 Watts, and while CPU power consumption is much more variable, it too tops out just a bit higher.

But regardless of the benchmark used, the end result is the same: the M1 SoC is delivering all of this performance at ultrabook-levels of power consumption. Delivering low-end discrete GPU performance in 10 Watts (or less) is a significant part of why M1 is so potent: it means Apple is able to give their small devices far more GPU horsepower than they (or PC OEMs) otherwise could.

Ultimately, these benchmarks are very solid proof that the M1’s integrated GPU is going to live up to Apple’s reputation for high-performing GPUs. The first Apple-built GPU for a Mac is significantly faster than any integrated GPU we’ve been able to get our hands on, and will no doubt set a new high bar for GPU performance in a laptop. Based on Apple’s own die shots, it’s clear that they spent a sizable portion of the M1’s die on the GPU and associated hardware, and the payoff is a GPU that can rival even low-end discrete GPUs. Given that the M1 is merely the baseline of things to come – Apple will need even more powerful GPUs for high-end laptops and their remaining desktops – it’s going to be very interesting to see what Apple and its developer ecosystem can do when the baseline GPU performance for even the cheapest Mac is this high.

Benchmarks: Whatever Is Available SPEC2006 & 2017: Industry Standard - ST Performance
Comments Locked

682 Comments

View All Comments

  • briceio - Wednesday, November 18, 2020 - link

    Oh crap, I just sold my MBP16, my Apple TVs, my iMac, and the iPad Pro of my wife... thinking Apple was going anywhere those last years... speak about good decisions & timing.
  • dontlistentome - Wednesday, November 18, 2020 - link

    Going to buy one, mostly out of geeky fascination for new stuff (even if it looks and acts like old stuff).
    Re the power consumption - does read a little like you're disappointed by this, lots of excuses/reasons for it being broadly in line to what's already out there at the low power end. Would love to see a Zen 3 laptop running an external display (lid shut) benchmarked as a comparison. Would there be any difference? I suspect not...
  • dizzynosed - Wednesday, November 18, 2020 - link

    Me too. Which one u will buy. I will go for the cheapest airbook.
  • joms_us - Wednesday, November 18, 2020 - link

    It is laughable to see how you continue to use Geekbench and the primitive version of Spec to compare ARM to x86 counterparts and then tout how godly superior it is. Just look at the huge discrepancies between native and rosetta mode. That is why you should compare two processors with same OS or same architecture (be it emulated)
  • dizzynosed - Thursday, November 19, 2020 - link

    Why? Why should we not compare how fast can it accomplish a task?
  • abufrejoval - Wednesday, November 18, 2020 - link

    Honestly, I am perhaps most impressed with how well the Ryzen 4800U did in Cinebench, especially the multicore. Sure, it's 8 big cores vs. probably just 4 big ones on the M1, but it's Zen 2 and 7nm so there is still potential to reduce the gap.

    And when you look at Geekbench results, there is one observation that sticks out very visibly and applies to both Geekbench 4 and 5:

    Windows results for identical hardware are the worst, significantly bettered by Linux result and again trumped by MacOS results.

    The explanation: The compilers are simply not the same and it shows.

    My Ryzen 7 5800X stays shy of 1700 on Windows for single score, but goes beyond on Linux.
    The first leaks in excess of 2000 on Ryzen 5000 were all on "MacOS/iMacPro1,1" or Hackintoshs.

    I'd guess they are using a Microsoft compiler for Windows, GCC on Linux and LLVM on MacOS.

    So to avoid comparing apples to lemons you need to compare the M1 to an 4800U Hackintosh, or better yet, Linux on both.

    Alas, without Linux M1 is useless to me. Shame, because the silicon and the box seems pretty nice, apart from that partially eaten fruit that's turned a rather less appetizing black over time.

    I am ready to bet a case or two of beer, that if Apple sold M1 to PC makers and opened their M1 hardware up to run Windows and Linux/Android for ARM, that would outsell PC running MacOS by far.
  • milli - Wednesday, November 18, 2020 - link

    That's exactly the thing that bothers me about Geekbench but this fact is mostly missed by the community.
    It is kind of funny that the Anand staff thinks it can draw so many conclusions about the underlying chip performance all the while running different OS' on these CPU's. Obviously, for now, running anything else than macOS on M1 is far fetched but as you say, you can run Hackintosh on AMD. If not that, then at most it's a platform comparison.
    Even running SPEC with the same compiler is up for debate vs optimized compilers.
  • blackcrayon - Wednesday, November 18, 2020 - link

    I'm going to guess this isn't much of an issue, if it were, Prime Labs themselves wouldn't keep it a secret. You don't think they've tested the same chips running on different OS's (wherever possible)?
  • blackcrayon - Wednesday, November 18, 2020 - link

    (primate labs)
  • thunng8 - Wednesday, November 18, 2020 - link

    All the 2000+ results on hackintoshes were wildly over clocked to 6ghz+. Geekbench does not run any faster on macOS compared to windows. Linux does seem to run a bit faster than windows though

Log in

Don't have an account? Sign up now