How could you study how Apple silicon CPU cores are used to run code? Comparisons between Activity Monitor, Xcode Instruments, and powermetrics.
AsmAttic
Lightweight virtualisation has come to Apple silicon Macs. How well does it work, though? Are there any significant limitations?
Select a test, time it, and compare the result with those from other systems. Choose whether to use a synthetic or application benchmark, and don’t forget your confirmation bias.
Which is faster, a MacBook Pro 16-inch with an M1 Pro, or a Mac Studio with an M1 Max? Tests cover P and E cores, Neural Engine, SSD and more.
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?
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.
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.
The Eclectic Light Company 