It delivers detailed weather forecasts for days in advance, and real-time manipulation of elaborate textured 3D models. But more mundane tasks may not get any quicker.
performance
In Activity Monitor, % CPU isn’t on a scale of 0-100. In M1 Macs, it also makes no distinction between E and P cores, nor does it allow for their changing frequency.
All disks cache data to be written, which makes benchmarking them tricky. It has more serious consequences which macOS tries to allow for in file systems and backups.
When running some tasks confined to E cores, the original M1 chip from 2020 completes them significantly quicker than an on an M1 Pro. Here’s the detail.
Users and other processes have very limited control over which threads are run on which type of core. As Apple Silicon develops, this is an area set for change.
From the anatomy of the CPU cores, to the queues of threads in GCD, and assignment to a core cluster, this details how threads are managed for the M1 series chips.
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?
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.
The Eclectic Light Company 