Why can’t the taskpolicy command tool be used to promote software to be able to run on the M1 chip’s Performance cores? Does it change QoS?
performance
Activity Monitor’s Memory view is the perfect place to watch for memory problems, such as a leak. Demonstrated here in macOS 12.0.1 and 12.1.
An accessible summary of the CPU cores in M1 chips, and how they appear to be managed by macOS to get the best for different classes of process.
Results from running 10-70 identical compute-intensive processes on M1 chips shows the differences in strategy between background and high priority settings.
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.
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 Eclectic Light Company 