How you can use the taskpolicy command to confine all the threads of a process to the E cores, as a brake, but there’s no accelerator in macOS.
Activity Monitor
How can the two E cores in an M1 Pro or Max equal performance of the four in the original M1? Why does running two threads complete in half the time taken to run one?
Threads, GCD and core allocation in Apple silicon explained. How thread priority is baked into code, and how important it is to performance.
P cores are conventional in that they can deliver excellent performance at maximum frequency, but with high power use. E cores may take 4 times as long for a task, but use less than a third of the energy.
How to interpret various measurements reported in Activity Monitor, from % CPU to Energy Impact, and how they can be compared across different Macs.
All about memory: different types, Unified Memory, Mach zones and the kernel, and how to manage system memory problems.
What to do with the Mac that either won’t go to sleep at all, or keeps waking up and discharging its battery? It’s pmset or Sleep Aid.
Using a test of compressing a 1 GB file with AppleArchive, measurements of power used by core clusters show how efficient using the E cores really is.
Using CPU % or Energy values in Activity Monitor appears to show that running code on E cores is less efficient than on P cores. Don’t believe a word of it.
How can you tell how much memory is being used by the GPU when both CPU and GPU use Unified Memory? Does it matter anyway?
The Eclectic Light Company 