Some apps and other code doesn’t appear to run faster on M1 chips, and some even runs more slowly. Could this be a result of it not using the best acceleration for vectors and matrices?
M1 Max
Assigning ownership to an external bootable disk doesn’t always work in Recovery mode on an M1 Mac. But there’s an easy workaround.
Most users won’t have noticed, but Recovery now works quite differently on M1 series Macs than it did in Big Sur. Here’s a detailed explanation of the changes.
Does your M1 Mac run more slowly when it’s on battery power, or with Low Power mode enabled? An exploration of effects on its CPU cores provides an unexpected answer.
The E cores on the original M1 and M1 Pro chips appear to be managed quite differently, with respect to the performance of background processes at low QoS.
Apple’s first quad-core chip, the A10 launched 5 years ago, had 2 P and 2 E cores, but could only run one type of core at a time. We’ve come a long way since then.
Obtaining estimates for individual P and E core performance of processes run mainly in an ALU and those using floating-point and SIMD gives further insight and confirms the cores haven’t changed from M1 to M1 Pro.
How does macOS load processes onto the cores in M1 series processors? Are its policies similar between the original M1 and the M1 Pro?
Passing your Mac on to a new owner has got much easier and more reliable in Monterey – so long as it has got a T2 or M1 series chip.
Geekbench 5 scores for the M1 Pro are around 2800 single- and 12500 multi-core. Do they represent maximum performance, though?
