Apple’s M1 processor is a world-class desktop and laptop processor—but when it comes to general-purpose end-user systems, there’s something even better than being fast. We’re referring, of course, to feeling fast—which has more to do with a system meeting user expectations predictably and reliably than it does with raw speed.
Howard Oakley—author of several Mac-native utilities such as Cormorant, Spundle, and Stibium—did some digging to find out why his M1 Mac felt faster than Intel Macs did, and he came to the conclusion that the answer is QoS. If you’re not familiar with the term, it expands to Quality of Service—and it’s all about task scheduling.
More throughput doesn’t always mean happier users
There’s a very common tendency to equate “performance” with throughput—roughly speaking, tasks accomplished per unit of time. Although throughput is generally the easiest metric to measure, it doesn’t correspond very well with human perception. What humans generally notice isn’t throughput, it’s latency—not the number of times a task can be accomplished, but the time it takes to complete an individual task.