Huge Memory Bandwidth, but not for every Block

One highly intriguing aspect of the M1 Max, maybe less so for the M1 Pro, is the massive memory bandwidth that is available for the SoC.

Apple was keen to market their 400GB/s figure during the launch, but this number is so wild and out there that there’s just a lot of questions left open as to how the chip is able to take advantage of this kind of bandwidth, so it’s one of the first things to investigate.

Starting off with our memory latency tests, the new M1 Max changes system memory behaviour quite significantly compared to what we’ve seen on the M1. On the core and L2 side of things, there haven’t been any changes and we consequently don’t see much alterations in terms of the results – it’s still a 3.2GHz peak core with 128KB of L1D at 3 cycles load-load latencies, and a 12MB L2 cache.

Where things are quite different is when we enter the system cache, instead of 8MB, on the M1 Max it’s now 48MB large, and also a lot more noticeable in the latency graph. While being much larger, it’s also evidently slower than the M1 SLC – the exact figures here depend on access pattern, but even the linear chain access shows that data has to travel a longer distance than the M1 and corresponding A-chips.

DRAM latency, even though on paper is faster for the M1 Max in terms of frequency on bandwidth, goes up this generation. At a 128MB comparable test depth, the new chip is roughly 15ns slower. The larger SLCs, more complex chip fabric, as well as possible worse timings on the part of the new LPDDR5 memory all could add to the regression we’re seeing here. In practical terms, because the SLC is so much bigger this generation, workloads latencies should still be lower for the M1 Max due to the higher cache hit rates, so performance shouldn’t regress.

A lot of people in the HPC audience were extremely intrigued to see a chip with such massive bandwidth – not because they care about GPU or other offload engines of the SoC, but because the possibility of the CPUs being able to have access to such immense bandwidth, something that otherwise is only possible to achieve on larger server-class CPUs that cost a multitude of what the new MacBook Pros are sold at. It was also one of the first things I tested out – to see exactly just how much bandwidth the CPU cores have access to.

Unfortunately, the news here isn’t the best case-scenario that we hoped for, as the M1 Max isn’t able to fully saturate the SoC bandwidth from just the CPU side;

From a single core perspective, meaning from a single software thread, things are quite impressive for the chip, as it’s able to stress the memory fabric to up to 102GB/s. This is extremely impressive and outperforms any other design in the industry by multiple factors, we had already noted that the M1 chip was able to fully saturate its memory bandwidth with a single core and that the bottleneck had been on the DRAM itself. On the M1 Max, it seems that we’re hitting the limit of what a core can do – or more precisely, a limit to what the CPU cluster can do.

The little hump between 12MB and 64MB should be the SLC of 48MB in size, the reduction in BW at the 12MB figure signals that the core is somehow limited in bandwidth when evicting cache lines back to the upper memory system. Our test here consists of reading, modifying, and writing back cache lines, with a 1:1 R/W ratio.

Going from 1 core/threads to 2, what the system is actually doing is spreading the workload across the two performance clusters of the SoC, so both threads are on their own cluster and have full access to the 12MB of L2. The “hump” after 12MB reduces in size, ending earlier now at +24MB, which makes sense as the 48MB SLC is now shared amongst two cores. Bandwidth here increases to 186GB/s.

Adding a third thread there’s a bit of an imbalance across the clusters, DRAM bandwidth goes to 204GB/s, but a fourth thread lands us at 224GB/s and this appears to be the limit on the SoC fabric that the CPUs are able to achieve, as adding additional cores and threads beyond this point does not increase the bandwidth to DRAM at all. It’s only when the E-cores, which are in their own cluster, are added in, when the bandwidth is able to jump up again, to a maximum of 243GB/s.

While 243GB/s is massive, and overshadows any other design in the industry, it’s still quite far from the 409GB/s the chip is capable of. More importantly for the M1 Max, it’s only slightly higher than the 204GB/s limit of the M1 Pro, so from a CPU-only workload perspective, it doesn’t appear to make sense to get the Max if one is focused just on CPU bandwidth.

That begs the question, why does the M1 Max have such massive bandwidth? The GPU naturally comes to mind, however in my testing, I’ve had extreme trouble to find workloads that would stress the GPU sufficiently to take advantage of the available bandwidth. Granted, this is also an issue of lacking workloads, but for actual 3D rendering and benchmarks, I haven’t seen the GPU use more than 90GB/s (measured via system performance counters). While I’m sure there’s some productivity workload out there where the GPU is able to stretch its legs, we haven’t been able to identify them yet.

That leaves everything else which is on the SoC, media engine, NPU, and just workloads that would simply stress all parts of the chip at the same time. The new media engine on the M1 Pro and Max are now able to decode and encode ProRes RAW formats, the above clip is a 5K 12bit sample with a bitrate of 1.59Gbps, and the M1 Max is not only able to play it back in real-time, it’s able to do it at multiple times the speed, with seamless immediate seeking. Doing the same thing on my 5900X machine results in single-digit frames. The SoC DRAM bandwidth while seeking around was at around 40-50GB/s – I imagine that workloads that stress CPU, GPU, media engines all at the same time would be able to take advantage of the full system memory bandwidth, and allow the M1 Max to stretch its legs and differentiate itself more from the M1 Pro and other systems.

M1 Pro & M1 Max: Performance Laptop Chips Power Behaviour: No Real TDP, but Wide Range
Comments Locked


View All Comments

  • web2dot0 - Tuesday, October 26, 2021 - link

    You just made his case. 😂
  • melgross - Monday, October 25, 2021 - link

    We’re all ready seeing optimized software from Blackmagic, and others. Blackmagic is claiming anything from 2 times to over 7 times performance gains in Resolve 17.4 with the 32 core Max.

    Apple also has a power mode that we can access which will turn the fans to max level for extra performance. I’m looking to try that when my 16” comes in a few days. I wonder if that feature was tested, as it wasn’t mentioned.

    Gaming, well, yeah. Over the decades most ports were bad. I don’t have any thought that the ones tested here were much better. Then running under Rosetta 2, as good as it is, isn’t helping.
  • daveinpublic - Monday, October 25, 2021 - link

    Huh, nice way to hijack the top comment.
  • name99 - Monday, October 25, 2021 - link

    So nothing changes.
    Gamers have always hated Apple. Doesn't change.
    Developers have been uninterested in Apple. Probably doesn't change.

    None of this matters to Apple, or most of its customers. Doesn't change.

    *Perhaps* Apple will make some attempt to grow Arcade upwards, but honestly, why bother? Almost all the ranting about gaming HW in threads like this is trash talk and aspirational; it does no translate into purchases, certainly not of Apple HW, and usually not of Wintel HW. It's no different from the sort of comments you might read on a Maserati vs Ferrari comment board -- and as uninteresting and unimportant to either the engineers at both companies, or most of the *actual* customers.
  • web2dot0 - Tuesday, October 26, 2021 - link

    Developers love MacBookPro what are you talking about?!?
  • mlambert890 - Tuesday, October 26, 2021 - link

    He's talking about *game developers* targeting MacOS. Not that in developers in general tend to like MacBooks (although certainly not Windows developers obviously)
  • TheinsanegamerN - Tuesday, October 26, 2021 - link

    Apple developers love macbook pros. The rest of the world sees them for the overpriced shiny facebook machines they've become. Gone are the days of the 2010 era tank macbook pros that lasted forever, chromebooks have better build quality and longer lifespans then modern apple products.
  • steven4570 - Friday, October 29, 2021 - link

    "The rest of the world sees them for the overpriced shiny facebook machines they've become. "

    Not really
  • Hrunga_Zmuda - Monday, October 25, 2021 - link

    It's not M1X. There are two chips, M1 Pro and M1 Max.

    I'm guessing that next year, the entry level chips will be M2 and the big boys will be M2 Pro and M2 Max.
  • TedTschopp - Monday, October 25, 2021 - link

    The money in the gaming space is in mobile gaming, not in AAA gaming, and Apple is the leader in Mobile Gaming Revenue. So the classic pattern here would be for them to leverage themselves from the leader in the low-end market into a leader in the high-end market.

    And with their first attempt at a gaming class machine, they came out with something in the first quartile. Next year, when the M2 Pro and Max, my guess is that they will be accelerating faster then their competition as their development and design processes have been designed to out compete mobile competitors, not desktop competitors like Intel and NVidia.

Log in

Don't have an account? Sign up now