Since Catalina, reports of Time Machine backups slowing to a crawl have become common, but the reasons are unclear. It’s time for Apple to inform us.
performance
Running processes at different Quality of Service affects their performance differently on Intel and M1 Macs. This explains what happens.
macOS manages the loading and frequency of M1 cores according to the QoS set, and rules which differ between the original M1 and the M1 Pro.
How the two Efficiency cores in the M1 Pro and Max chips can match the performance of all four E cores in the original M1.
How can the two E cores in an M1 Pro/Max apparently match the performance of the four in the original M1? Answers, please.
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.
If your Mac slows to a crawl, don’t just reboot it. Here’s how to discover what the likely cause is, and a structured approach to recovery.
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?
The Eclectic Light Company 