Benchmarking the Apple M1 Max
tlkh.dev
tlkh.dev
This mirrors my experience with my M1 Max: Absolutely amazing battery life and performance in a laptop. I’m thrilled to have it. Huge step up from last gen Apple laptops.
But at the same time, it feels like some of the rhetoric around the performance claims got a little out of hand in the wake of the launch. It’s fast, but it’s not actually crushing my AMD/nVidia desktop like a lot of news outlets were suggesting it would.
In fact, a lot of the GPU tests here show more or less what I’ve seen: That Apple has matched the power/performance of other leading-edge GPU hardware:
> Pretty much what we would expect, with the M1 Max having about 8x less performance, but at 8x less power, so performance per watt is surprisingly quite comparable between the two.
This is actually an impressive accomplishment out of Apple. I’m just afraid it might get overshadowed by the fact that it doesn’t live up to some of the fairly extreme performance claims that got tossed around in the days following the launch.
Apple hasn't even released the Pro desktop stuff yet.
That doesn't diminish how excellent Apple Silicon is for Macbook users (and Mac Mini users).
It's just an exciting time when laptops (with the right silicon) can do more than ever before, reducing the need to have a desktop for a lot of tasks, and also... largely not a great time to be using Intel chips. (Alder Lake is very high performing, but power hungry and desktop only.)
I wonder if future perf gains will come, game console-style, from areas besides general purpose computation -- specialized instructions / cores for specialized tasks.
Imagine an entire core optimized for Safari and its Javascript engine. Their next chip is called the "M1 Marathon Edition" and you get 36 hours of real-world battery life with Safari. And/or the iWork suite. And maybe they have a behind the scenes collab with Slack and select other app makers so that they can be a part of the "Marathon" program too.
I dunno, just spitballing. Not saying that's likely or even what I'm pining for, just one possible avenue once they've plucked all the low-hanging general purpose computing fruit.
What if somebody on the Intel/AMD side of things includes some optimizations for SSE, AVX, etc? Are they punishing everybody else?
At any rate, my idea was less than half baked and again, not exactly something I'm pining for. Was just thinking about things Apple might conceivably be able to try with their unique vertical integration.
Hyper-optimizing for a particular application means the way that particular application works gets accelerated, but not things in general. Sure, if a browser behaved identically to Safari, it too would potentially experience the speed up barring any weird microcode/firmware that only allows those extensions to be used by Apple-signed binaries which is a whole 'nother level of nightmare. Stepping outside of that highly optimized path is essentially a penalty though as it by definition wouldn't be so highly optimized. And once that optimized path has been etched into the silicon, there's no real updating it unless we move to CPUs being more like FPGAs which isn't likely to happen.
Intel doesn't forbid compilers from generating code for SSE or AVX.
Apple _does_ forbid Chrome from using energy management and other APIs for no other reason than to keep it less efficient than Safari.
That is unfair and I would not support that behavior whether talking about private software APIs or private hardware instructions. What I was half-assedly imagining wouldn't be anything like that.
(Although, FWIW, Chrome has private APIs too: https://blog.chromium.org/2021/01/limiting-private-api-avail... Different use case, but still.)
I've been having trouble figuring out exactly which private bits and bobs Webkit might be taking advantage of on MacOS.
Other commenters are suggesting that Apple's intent is to keep Chrome and other third-party apps from matching Safari's energy efficiency.
But as you say, I'm not sure that makes strategic sense. If that is true, Apple is essentially crippling most Mac use cases just to benefit Safari. That really would not seem to be in Apple's best interests.
I am a developer, but not a iOS/MacOS developer. So I have followed this sort of thing only very loosely over the years.
But whenever I have heard about grumblings about private Apple-only APIs being used by blessed first-party Apple apps on iOS, it seems to me that the explanation was always that the private APIs either:
1. posed some sort of security issue
2. were simply not yet stable enough to expose to third-party apps
As every developer knows, publicly exposing any API represents a maintenance burden: you're committing to support that API and keep it stable for X number of years. In general you see this kind of pattern a lot: a platform developer dogfoods APIs internally for some period of time before they're stable enough to expose publicly.
E.g even on the M1 Pro/Max, you're going to get much better performance and battery if you're using a video editor that supports prores decoding.
It's already possible to target GPUs in-browser directly; and most older HTML primitives were recast in terms of GPU operations around the time of the original iPhone. The only thing I can think of that's still been left on the table is rendering vector geometry on-GPU; but most sites don't redraw so much as to make this a huge performance win.
Video decode has been offloaded to hardware for decades as well. The only reason to decode video on-CPU is if you're decoding crazy-old formats[0] that don't have hardware decoder blocks present for them.
The other huge problem is networking - which is also heavily hardware-optimized and has been for a while. Large assets mean keeping your Wi-Fi or LTE baseband on for longer. You could mitigate this with compression; which can be hardware optimized... though I'm not sure how much of a benefit that provides outside of game consoles[1].
[0] In my personal experience: I wrote a Sorenson H.263 decoder for Ruffle. Right now it not only executes on-CPU, but blocks the event loop main thread. However, the video files in question are so low-quality that this isn't a significant problem for most Flash movies and everything works fine (though I do want to try on-GPU video decoding at some point).
[1] Current-gen game consoles (PS5/XSeries) have hardware decompression blocks. However, the intent is to quickly decompress gigabytes worth of data quickly; most websites aren't nearly that bloated.
I'm not. Let them all scramble and pull out the big guns to try to compete. That's capitalism at it's finest, which isn't exactly what we've been seeing in the CPU space for the prior decades. We got lucky that AMD caught Intel with their pants down recently (if only because it strengthens AMD and makes them a better competitor), but a duopoly isn't necessarily what I would consider a good market condition for progress (as we've seen with iOS vs Android). Lots of different experiments with feedback from people on what they find good would be much preferable, and while a constrained CPU such as Apple's isn't perfect, it does represent more choice and pressure on other players to evolve in ways they may have been resistant to previously.
> And maybe they have a behind the scenes collab with Slack and select other app makers so that they can be a part of the "Marathon" program too.
RIP the general purpose computer. :(
> And maybe they have a behind the scenes collab with
> Slack and select other app makers so that they can
> be a part of the "Marathon" program too.
RIP the general purpose computer. :(
Since heterogenuous cores are now a mainstream thing, with a mixture of full-throttle and performance-minded cores on a single die, and the performance cores may be hitting a wall until we get to smaller processes, perhaps the next frontier could be efficiency.
Remember how some software proudly displayed those "optimized for MMX" or "optimized for 3DNow!" badges back in the day? What if there was something like that for apps that optimized for those efficiency cores, and what if the efficiency cores met them halfway by implementing some app-friendly stuff in hardware? Sort of like how some common Javascript string ops have dedicated CPU hardware dedicated to them now.
Anyway, yeah. I'm probably just re-inventing CISC all over again, badly.
I don't think that would be worth it. What's the point of 36 hours of battery life? How often do you need more than 12 hours of life on battery? Increasing the maximum battery life only makes sense when it also increases battery life for the more power-hungry workload (which is where you're likely to reach the limit), why bother building dedicated hardware for a specific workload that's already beyond what you need?
> reducing electricity usage reduces costs and overall emissions in to the planet
You're going to need a looooooooooooooooong time for the electricity usage reduction to compensate for the enormous energy cost of manufacturing a new laptop. If you care about the climate, don't buy a new laptop if your previous one is still running fine, there's just no way energy efficiency is going to be worth it.
Considering that some of the magic in these things is the shared, local memory with a very wide bus it would seem obvious that trying to go multi chip would indeed be a massive headache in this regard
[0]: https://architosh.com/2021/10/apples-new-m1-pro-is-chop-vers...
All of the M1 devices have been monolithic dies so far.
This fact however makes "performance per watt" comparisons misleading between different processors designed for different environments (e.g. M1 vs AMD Desktop). It takes a more power to get that much extra perf, conversely and the more under-appreciate part IMO reducing the speed a little can save a ton of power/heat if the chip is currently running at the higher power portion of the curve.
On a desktop machine most people would want them to tune for performance at quite a substantial power efficiency cost so of course a desktop chip most probably is less power efficient per unit of compute. You don't need to power it with a battery after all and there's heaps more cooling capacity in a bigger form factor so why optimise for that?
For comparison, the 3090 has almost 1TB of memory bandwidth.
Per chiplet.
Zen 2 was a must-have upgrade over Zen+ and it was a 10% IPC increase.
To be clear - Apples M1 hardware is good, even great. It's just that Apples marketing hype is so over the top, and so many people buy into it so hard that people (such as me) still feel the need to bring it down to earth.
Except it's not. The performance per watt is significantly better on average. Only one of the examples in this post really talked about power usage and that example also says that the 3090 is using a special compiler and gets to use the special tensor cores in the 3090, but for the M1 Max it wasn't able to use the neural cores or the special compiler and still achieves a similar performance per watt.
If you look at more detailed benchmarks from Anandtech:
> In the SPECfp suite, the M1 Max is in its own category of silicon with no comparison in the market. It completely demolishes any laptop contender, showcasing 2.2x performance of the second-best laptop chip. The M1 Max even manages to outperform the 16-core 5950X – a chip whose package power is at 142W, with rest of system even quite above that. It’s an absolutely absurd comparison and a situation we haven’t seen the likes of.
https://www.anandtech.com/show/17024/apple-m1-max-performanc...
But it's kind of a strained comparison. Power usage doesn't scale linearly with performance for any CPU (power consumption scales with the square of voltage) so squeezing the last 20% of performance out of a desktop chip could require doubling the power consumption. Which is actually find for a desktop because I really don't care if my CPU consumes 100-200W for a few minutes while doing a compile. But trying to compare performance-per-watt between two parts tuned for different parts of the power/efficiency curve is always going to be misleading.
If we wanted to compare straight across, comparing to AMD's mobile Ryzen parts would make more sense.
AMD has a 35W mobile part that isn't all that far behind the M1 parts: https://browser.geekbench.com/v5/cpu/11001445
Even using Geekbench as the benchmark, we see that the M1 Pro multicore score is around 12650, which is 58% better than the Ryzen 9 5980HS you linked.
1. https://www.anandtech.com/show/17024/apple-m1-max-performanc...
In other news, processor that draws more power on a more efficient process is faster. More news at seven.
I assume SPECfp specifically scales really well with memory bandwidth/latency.
Regardless, I was talking about GPU performance in my comment (because GP was talking about GPU performance) which all of the replies seem to be ignoring.
The one advantage of the M1 Max's GPU is more memory.
The third party testing does show that the comparison is valid.
>The chips here aren’t only able to outclass any competitor laptop design, but also competes against the best desktop systems out there, you’d have to bring out server-class hardware to get ahead of the M1 Max – it’s just generally absurd.
https://www.anandtech.com/show/17024/apple-m1-max-performanc...
Right, and I acknowledged the battery life as amazing.
But currently, I can't buy an M1 Max desktop if I wanted to. So instead I have a 16" MacBook Pro semi-permanently attached to my monitor and keyboard at my desk. It's basically a desktop for me.
I don't expect a laptop to outperform my AMD/nVidia desktop workstation. And sure enough, it doesn't! But it comes surprisingly close for common tasks and I'm very happy to have it.
The problem with this take is this:
https://www.anandtech.com/bench/product/2685?vs=2613
This is mobile vs. desktop Zen 2 with the same number of cores. You give a CPU three times the power budget and it gets marginally faster. Because the last few hundred MHz of clock speed uses a ton of power, and that's it.
But then you have this:
https://www.anandtech.com/bench/product/2613?vs=2666
Nearly double the multi-threaded performance at the same TDP, because it has twice as many cores and it only has to give back the last few hundred MHz of base clock to do it.
A laptop with performance largely equivalent to <= 8-core desktops wasn't a novelty. What a desktop really gets you is the ability to have a lot more cores.
So sure, you can cherry pick one part of the SoC, match it up against one aspect of Chip X and try to make a point. OK, you win that one. I'm talking about what the SoC as a whole does while running near-silently off a battery.
Yes, a desktop gives you the ability to have more CPU cores. I'm sure that's what we'll get from whatever Apple decides to ship for its true Pro desktops.
People were primarily comparing it to desktop CPUs because of where we were in the release cycle. How does it compare to Zen 3? Well, Zen 3 laptops were still a few months away when the M1 was released, but Zen 2 desktops were only a single digit percentage faster than Zen 2 laptops, so how does it compare to Zen 3 desktops?
Meanwhile the primary real advantage of the M1 is that it uses less power. Compared to PC laptops, it's a somewhat less power. There are already PC laptops with 9+ hours of battery life (and no matter how little the CPU uses, you still have to run the screen and everything else), so the practical impact of this isn't enormous, but it's there. But if you compare the power consumption to PC desktops, OMFG! Except that nobody really cares about the power consumption of PC desktops. That's why they triple the power consumption to eek out 8% more performance.
A lot of this is also attributable to how good Apple's marketing is. I don't know if they did this on purpose, but people keep publishing SPEC benchmarks for comparison with PCs. Part of this is that a lot of the ordinary benchmark software either doesn't run on Mac at all or there was no native ARM version available yet. But SPEC was put together by a consortium of server vendors. Their incentive is show that their POWER and Xeon processors are worth the fat premium over regular desktop CPUs. So the suite skews heavy to benchmarks limited by memory bandwidth, because big servers will have like 16 times more memory channels than a desktop.
Then Apple shows up with this SoC that has a ton of memory bandwidth because it's necessary to feed the GPU and it stomps all over those specific benchmarks. Then it's OMFG again even though those results aren't actually typical because most workloads aren't limited by memory bandwidth.
It's not a bad chip. The level of hype is just extraordinary.
> There are already PC laptops with 9+ hours of battery life
Not when they're actually doing anything. To compete with what the M series chips bring, you need a discrete GPU and a very hungry CPU. Such a machine does not get 9+ hours of battery life.
> The point is that we already had this. Both the CPU and GPU are competitive with existing CPUs and GPUs. Which is a first in a long time for anybody outside of AMD/Intel/Nvidia. But "competitive" and "dramatically better" are not the same thing.
Right, you already had something like this in multiple discrete components that consume a huge amount of battery life when cobbled together into one system. My entire point has been that the impressiveness of the M series chips comes from their efficiency and what they are able to do holistically in a single SoC.
> A lot of this is also attributable to how good Apple's marketing is
Sigh. Alright I know what I'm dealing with now. Good day to you sir!
Then you get results that are equivalent rather than superior.
> Not when they're actually doing anything.
Yes, when they're actually doing anything. The M1 Macbooks get around 16 hours. Under the same kind of load a similarly performing PC laptop might get around 10 hours. Other PC laptops will get 16 hours (or more) by having a lower TDP and then being slower, especially on multi-threaded workloads.
This obviously only matters to people who care about not just long, but very long battery life, and very high performance, and aren't willing to make the weight trade off of getting one with a bigger battery.
> My entire point has been that the impressiveness of the M series chips comes from their efficiency and what they are able to do holistically in a single SoC.
It has very little to do with being in a single SoC. The CPU being able to use the memory bandwidth which is there for the GPU is a neat parlor trick but it only matters if memory bandwidth is the bottleneck, which it usually isn't.
> Sigh. Alright I know what I'm dealing with now.
You don't think that Apple has excellent marketing? They've done this for decades. They make a competitive product and then convince their customers that alternatives are dramatically inferior by pointing to narrow edge cases.
The part where the efficiency is radically better than competing parts has everything to do with it being an integrated SoC.
> Then you get results that are equivalent rather than superior.
Equivalent to what? Your desktop at 5+ times the wattage? A Windows laptop with half the battery life and twice the weight?
> Yes, when they're actually doing anything. The M1 Macbooks get around 16 hours. Under the same kind of load a similarly performing PC laptop might get around 10 hours. Other PC laptops will get 16 hours (or more) by having a lower TDP and then being slower, especially on multi-threaded workloads.
Ok this is so ambiguous as to be nearly meaningless. 10 hours of what? At the least you're conceding that in this undefined workload the MacBook gets 6 more hours, which again, has been my whole point. The holistic efficiency is the whole story.
> This obviously only matters to people who care about not just long, but very long battery life, and very high performance, and aren't willing to make the weight trade off of getting one with a bigger battery.
"Only people who want better performance and better battery life should get an Apple Laptop" ... is that basically what you're saying here? Because we might just finally be in agreement.
If you don't care about performance or battery life or weight there are plenty of Windows options available. This is true.
What makes you think that? The CPU is about the same speed as other CPUs, the GPU is about the same speed as other GPUs, and it uses less power in no small part because it's the first thing to use TSMC 5nm.
Being an SoC allows you to save a certain amount of overlap, e.g. you don't need separate memory controllers for the CPU and GPU, but none of that stuff uses a significant amount of power.
> If you don't care about performance or battery life or weight there are plenty of Windows options available.
It's not matter of not caring. You can get PC laptops with similar performance and similar weight and 10 hours of battery life instead of 16. Ten hours is not exactly oppressive. If you really, really need sixteen, you can trade it against weight or performance at your option -- it's not necessary to do both.
Or you could wait a few months for PC laptops on TSMC 5nm which will have better power efficiency.
It absolutely uses more power to have things on separate dies. Why do you think monolithic designs like this are preferred for mobile first products? It's certainly not because it's cheaper or easier. SoCs like this typically have lower yields and higher costs--you do it because in return you can squeeze out better power and efficiency while also saving space on the board.
> It's not matter of not caring. You can get PC laptops with similar performance and similar weight and 10 hours of battery life instead of 16.
This is just so emphatically not true though. Like I'm going to need to see the workload you're referencing where a device with similar benchmarks across the board (CPU and GPU) gets 10 hours of real world battery life without weighing 5 lbs.
Like I have in my possession as a daily driver a 2020 MacBook Pro that uses an Intel IceLake chip--fairly recent tech! If I'm doing my actual work on it--a bit of Docker, Chrome, and an IDE--I'm lucky to make it much past lunch. A fairly recent Intel chip, that gets positively embarrassed performance-wise by an M1, and can barely turn in 6 hours of real usage.
I want to see this system you have that performs like an M1 and turns in 10 hours of real world battery usage.
> Or you could wait a few months for PC laptops on TSMC 5nm which will have better power efficiency.
You could have already had it for well over a year now with Apple. And by the time this mythical laptop you're speaking of arrives, Apple might have already moved on to the next node. But hey, it's your life not mine. Keep waiting if it pleases you.
It used to be different, but now frequency is so close to the absolute limits that adding more power doesn't help single core performance that much.
Super fast builds, and A huge productivity boost. I think it shows that if software is optimized for it, M1 can be/feel crazy fast.
Unfortunately, anything running with Roseta, will not feel that fast, as it's performance will be hobbled by the emulation layer.
So for me, its performance completely lives up to the hype. I don't think I'll need a new machine for a loooong time.
Live still doesn't have built-in bit bridging? (Of course, bit bridging doesn't come free.)
Firefox's M1 port actually got me to finally start transitioning out of chrome after being a fairly devoted chrome user since it released. It's the only third party browser on M1 macs that comes close to Safari in speed and handles window size changes (especially when video is playing) leagues better than Chrome.
However, part of me thinks this is Apple doing iterative rollout best - they could have created a 20-core desktop version of this in 2021 but will likely delay that to next year for the new Mac Pro and iMac Pro.
The other thing is price, the m1 max cost $5k here. You know what kind of PC you can get for that price? A 3080 MSRP is $700 and beat any mac GPU right ( and that's a GPU from last year ). 5900x cost $480.
do we know for a fact that a 90w Apple GPU would
perform 4x faster if it was running at 500w
I would certainly like to see Apple go nuts and make a true, cost-and-power-consumption-are-no-object world destroying GPU. If only as a halo product. But I wouldn't hold my breath.
At some point you are adding 90% more power use for 3% more performance.
The only reason I care about performance/watt is because I actually care about noise, heat and battery life. I'm not running a data center off a laptop so the cost benefits of performance/watt are not even a concern.
Its a nice chip but we shouldn't confuse the marketing for the actual benefits.
If a higher performance/watt but much lower absolute performance chip was released, I wouldn't be interested.
Yeah, all pretty major concerns?
I admit it's a pedantic comment but I was pulled in by use of "literally everything".
The point is at best I care about perf/watt
indirectly and the things I do care about can
be improved in other ways
You fairly quickly learn that dissipating kilowatts of watts of heat from something as tiny as a CPU die (or, more accurately, one particular subset of functional units from in a CPU core) is awfully difficult.
At some point, the CPU/GPU/etc need to be kept under a certain temp, which sets an upper bound on watts. So, no escaping watts/performance....
Okay, noise, _maybe_, but how are you proposing to improve heat and battery life without improving perf/watt? Your options for battery life are either to reduce performance, or to increase battery size (but, well, good luck with that; the 16" MBP is already as big as a laptop battery can practically be, as if it was any bigger you wouldn't be allowed take it on a plane). Your only option to reduce heat without improving perf/watt would be to reduce performance.
Performance/watt it not everything. It's not really even something.
It's a derivative concern.
The only reason I care about performance/watt is because I actually
care about noise, heat and battery life.
Presumably, all you really care about is raw performance then?
Well, OK, fair enough. We can all care about different things. But even though, performance/watt still rules: for all practical purposes the watts part constrains the performance part.
For a given power supply and cooling system, you can only draw and dissipate X number of watts. So you are back to the question of how much performance the system can provide given X watts.
Even no-compromises cooling solutions most would consider highly impractical (involving liquid nitrogen etc) run into this issue at some point. So yeah, you actually do care about performance/watt?
On GPUs, pretty much. It’s even called embarrassingly parallel for this reason.
Yes, with HBM3 you could go up to 5TB/s and in the future 6.4TB/s. To give a comparison a 3980 RTX Ti has ~900 GB/s with GDDR6x.
But just with everything we hit TDP or cost ceiling well before any technical barriers.
The answer is yes. Scaling with more cores running at the same frequency giving unlimited bandwidth. Yes it is pretty much linear for GPU.
I guess that is why most of the discussions is so tiring. Because this fact is not known.
So this would be great specifically for finetuning large transformer models like GPT-J, which requires a lot of memory but not a lot of compute. Just hoping for pytorch support soon..
In theory you could even push the 5700G to 128GB if you figured out a way to get ECC to work on it.
The BIOS doesn't set the shared memory. The BIOS sets the dedicated memory. The shared memory is set by the OS and driver as you need, and the only limit is how much memory you have and how much is used by other processes.
You can force any program to use shared memory by making dedicated memory low. As I said, these programs don't really choose to use it, it's a driver/OS responsibility.
The 5700Gs memory controller indeed can't go above 100GB/s. However 200-400GB/s is not what the M1 Max GPU can do, it's combined performance. You'd have to substract CPU performance. The M1 Max GPU would still be faster of course. But the premise is that GPU performance doesn't really matter.
I have the first M1 MBP pro 13” and have done a lot of data stuff on it. My experience was also that python flew - cpython on the M1 being almost as fast as pypy on my 2019 i7 laptop - and java compilation was much faster too. The CPU is fast and the memory is really fast.
The performance pain points though was anything involving containers, random 10-30 sec stalls in boot and app startup (I think it’s corporate firewall stuff) and a general preference I have for Linux desktop over OSX (yeah I’m a programmer).
But at this point it's really held back by Apple's software.
Anything related to Apple ID and iCloud regularly hangs 30-60 seconds, showing a spinner with no progress indicator whatsoever.
Apps randomly take 20 seconds to launch, maybe because of [1]?
The Open/Save dialog taking 30 seconds to show.
ControlCenter using 8GB of RAM to show a few sliders (I hope they fix that bug soon).
The scanning feature in Preview is so unreliable that I started using my Windows machine for scanning something on my HP all-in-one.
Some of those problems may be issues with 3rd party software (drivers), and others are just things that slipped through QA, and will hopefully be fixed in an update.
But some of the issues are structural issues, where Apple has made questionable decisions that means issues can never be fixed.
Eg. designing a security architecture that requires synchronously checking a binary signature during app startup with a web service is bound to cause performance issues.
Or the design of the XPC system, which uses asynchronous message passing between services that are implicitly launched on demand sounds nice in theory, but it has been the source of so many bugs, causing temporary or permanent app hangs that are impossible to debug. The system was introduced in macOS 10.7 (!) and it still doesn't work reliably! At this point I've lost hope it will ever work properly.
[1]: https://sigpipe.macromates.com/2020/macos-catalina-slow-by-d...
But it's not all or nothing. For example I've started using Syncthing instead of iCloud Drive for some use cases and that works surprisingly well (Syncthing isn't without flaws either, but at least it shows exactly what it's doing making it a lot easier to debug).
You could run it today if you wanted to, but there are a bunch of things that are missing.
XPC is not asynchronous; that's up to the individual caller. The synchronous methods are easier to debug for sure.
It's been some time since I dug into the internals of XPC, but my assumption was that the underlying protocol is asynchronous, and if you do sync calls the wrappers just do the waiting for you.
The problem is that it has a tendency to get stuck in some rare cases, where services just don't reply for some reason. Then the sync calls are the worst -- the UI of the app is completely frozen and there's nothing you can do except restart the app. If the problem is with an Apple service (like Apple ID) then the only way to fix it is to restart the Mac and hope it doesn't happen again.
You don’t seem to have a full grip on the reasons for the intermittent hangs you’re experiencing. Can I suggest two things?
1 Grab a sysdiagnose during one of the hangs and file a feedback report with Apple
2 Use the `sample` command line tool to see what’s actually hanging a particular process for yourself
I try to report all of the issues I see to Apple, but at some point there's nothing I can do except complain that Apple's frameworks are buggy.
The biggest problem with these bugs is that customers always seem to think it's an app bug, and there's nothing the app developer can do except hope that Apple fixes the issue. One early sandbox bug took Apple about 3 years to fix. To be honest I don't even know if they fixed it, it was never mentioned in a changelist, it's just that I stopped getting reports of the issue at some point.
That's interesting! I thought XPC was a wrapper around async mach messages. Do you have any pointers where I can learn more about this?
But it's a special wait that the scheduler and other systems know how to benefit from using vouchers/turnstiles/etc. If you look at spindump output you should see it.
Don't use "sample" if the issue could be multi-process or in the kernel, use "spindump".
On Safari that happens when you have lots of Bookmarks, History, Open Tabs etc.
I've got an M1 and M1 Pro and I've never seen anything like this, macOS in general has some long standing software bugs around the performance of apps like Music and Preview that I've seen hit on the M1 processor but they seem to make less of an impact to the usability compared to the Intel processors.
Not every time, mind you. Only about once in 50 times. Sometimes she goes for weeks without it. Sometimes it happens several times in a day.
My 2016 imac has some weird issues as well, like not supporting some of my keyboards when I use a nonstandard layout file (swedish dvorak)- even though they work just fine with apples own keyboards.
Apple has some issues with quality control. Things have gotten steadily worse since 10.5, even though I do enjoy the new features.
Not just weird things like the one above, but basic things like standard shortcuts not working when you have Swedish layout. Now I cant remember which one it was, but it was something that should do a common thing, but instead brought up the "search in the help files" instead.
I have been bitten by it every time I use a new mac or do a fresh install.
For anyone saying "I never see this" or "something's wrong with your system" - I've seen these sorts of problems, in some capacity or another, over ... 12 years, multiple macbooks and imacs, multiple OS versions, multiple internet providers, from various parts of the world. I think the folks saying "never affects me" simply do not notice this stuff. I don't know how/why you can't notice stuff like this, but I've been present where I've noticed people getting beach balls, I've pointed it out, and was told "oh, didn't see that". Not saying every single person is missing every single instance 100%, but I've no doubt this interrupts peoples' flow different from mine.
If I've paid $4k for a laptop and click a button, I don't expect to wait for... 1-2 seconds, then see a beach ball, then wait.... then wait some more... before a button click is recognized. It's better today than last year, and the year before, but... wtf... it's still there.
Now we seem to be at a point where the software is getting slower more quickly than the hardware is getting faster, so that following a hardware upgrade everything is a bit slower than it was following the prior upgrade.
Software sucks, and hardware is amazing.
Is this even possible? I don't think a 50k computer can guarantee no wait on software. How would any hardware prevent excessive software utilization?
Not that I never see them, but that cut them to under 5% the rate I'd been seeing them. Xcode still does it pretty reliably, but luckily I don't work in that much. Now if I see them it's usually because WhatsApp or Slack have gone insane, which they do every few weeks. Or some web app. Point is, there's usually one thing going nuts that causes it, it's not just a constant feature of my desktop even under light-ish load.
Some heavier stuff, like Android Studio with the Emulator running, might still beachball quite a bit. Dunno, been out of Android development for quite a while. I'm sure there are some workflows that still have the problem. The browser thing kept them from being a common feature of my personal experience, though.
The only slowness I’ve noticed has been related to the beta private relay
This is _infuriating_ as a user. There is no possible good reason for this.
I’ve never experienced any of these issues (multiple macs in various profiles).
Issues I've reported via Feedback Assistant:
1. Issue waking external displays. Typically 10+ seconds to wake my HDMI display, Thunderbolt is faster, but still a bit slow.
Slow wake of external displays might sound like a minor issue, and it is. What's not a minor issue is having all my windows slammed on top of each other on the Macbook's built-in display every time I wake from sleep.
2. No scaling for external non-4K monitors. I've got a 1440p 144Hz display, my options are tiny text, pixelated large text (decreased resolution) or install a third-party work around (https://github.com/waydabber/BetterDummy). The third-party work around breaks screen recording. Seems there's another bug in macOS where you can't use display mirroring and record screen at once - it crashes the screen capture tool.
3. Unresponsive Finder. Sometimes I can't drag and drop files. The rest of the UI works, but you cannot click and drag. No idea why.
4. Black screen (with cursor only) after wake from sleep. Think this is somehow related to clamshell mode, as I believe it enabled briefly when I plugged external displays in before opening the lid. Had to hard reset.
5. Audio popping. System wide. Interestingly there's no category for reporting sound issues in Feedback Assistant. Pretty crazy when you think about modern Apple's origins. Seems this is a pretty wide-spread issue. Theories I've seen have been related to Rosetta. However, I can confirm that arm64 binaries (e.g. Firefox) do occasionally lead to popping, but it may be that Intel binaries are running at the same time. It comes and goes. It's almost certainly a driver issue, doesn't sound like bad speakers, sounds like corrupt buffers.
Issues I haven't reported:
1. Text boxes not being responsive. As in, you can't click in them. I don't know if this is somehow related to the Finder issue. It may well be app specific, hence why I haven't reported it. However, I've observed it in Firefox and Jetbrains products.
2. Garbled rendering, particularly around fonts. Again, might be app specific. Main culprit is Slack. Restarting the app doesn't fix it, rebooting does though.
There's probably more that I'm forgetting. Honestly, this is a bit depressing. The M1 is a beast. If I worked on Apple's hardware team I'd be pretty peeved, because they've achieved something amazing and cruddy software is compromising the entire experience.
https://jott.live/code/blas_test.cc
I saw ~1.2tflops on the regular M1
git clone https://github.com/xianyi/OpenBLAS && cd OpenBLAS && make PREFIX=/opt/openblas install && curl https://jott.live/code/blas_test.cc | sed -n "/<code>/,/code>/p" | tail -n +2 | head -n -1 > blas_test.cpp
inspect blas_test.cpp file, and then...
g++ -I/opt/openblas/include/ blas_test.cc -lopenblas -std=c++11 -O3 -L/opt/openblas/lib/ -o blas_test && ./blas_test 512 512 512 100 100
and got a peak of about 192 gflops, averaging closer to 180. So yeah, the M1 is > 6x faster in this simple single-precision matrix test.
g++ -I/opt/intel/mkl/include/ blas_test.cc -lmkl_intel_lp64 -lmkl_gnu_thread -lmkl_core -lgomp -std=c++11 -O3 -march=native -L/opt/intel/mkl/lib/intel64 -o blas_test_mkl
Personally I'm kind of regretting the purchase. My 2015 Macbook Pro is faster than it.
Does this hold for the M1 Pro?
The performance claims have been a bit overblown in some quarters - it’s not going to replace a 5950X with a big GPU, and some of the rhetoric is a bit silly. But it’s surprisingly close - watching a silent laptop rip through a build faster than the 125W TDP i9-10900K we have in the office is pretty cool!
Even that is not true FP32 for 3090 as tensorflow uses Nvidia's AI32 by default for convolution.
Is the incredible performance of the M1 just going to enable a whole new generation of inefficient software?