M3 chips widen the gap between Pro and Max variants. They also change relative performance between P and E cores to make M3 CPUs more versatile.
vector processing
There’s more to getting best performance and energy efficiency on Apple silicon. These vary greatly depending on how apps are coded, as shown here.
If Apple offered to do much of the hard work of coding your app for you for free, and to optimise it for different Mac hardware, how could you refuse?
How to compare an undocumented if not secret co-processor? Using different tests that use very high power, and can result in strange patterns of core allocation. So how does the M3 Pro fare here?
Comparison with M1 variants, energy use with comparison between M3 Pro and Max, virtualisation, Game Mode, vector processing and matrix co-processing – all in summary.
Assessing throughput using tests of fast Fourier transforms and sparse Cholesky factorisation from the Accelerate library. Is there an AMX there?
Differences in vector processing performance between the M1 Max and M3 Pro, and in their use of power. Their frequency control is more complex.
Some apps and other code doesn’t appear to run faster on M1 chips, and some even runs more slowly. Could this be a result of it not using the best acceleration for vectors and matrices?
The Eclectic Light Company 