One of the most distinctive features of Apple silicon chips is that they have two types of CPU core, E (Efficiency) cores that are energy efficient but slower than the P (Performance) cores, which normally run much of the code in the apps we use. Apps don’t decide directly which cores they will be run on, that’s a privilege of macOS, but they register their interest by setting a Quality of Service, or QoS, which is then taken into account when they’re scheduled to run. With the introduction of Game Mode in Sonoma, CPU scheduling can now work differently, with E cores being reserved for the use of games. This article looks at another atypical situation, when running a macOS virtual machine (VM) assigned a set number of virtual cores. How does macOS Sonoma handle that?
As far as I know not to the same degree? For example I’m pretty sure Apple’s efficiency cores don’t do speculative execution or at least don’t do much of it.
AFAIK the x86 chips mostly just reduce the clock speed don’t they?
x86-64 doesn’t need efficiency cores because unlike ARM, it doesn’t care about limiting power draw.
ARM’s main appeal has always been ability to compute with minimal current (I think the first ARM processor consumed no power).
I think the first ARM processor consumed no power
Now that would be some efficiency aight.
I recall something about operating on leak current alone, which is probability where you got that from.
@Skelectus @ultratiem yes, that happened. It first worked on residual energy from the board it was on. It was a funny accident actually. They forgot to turn on the power supply, but it was working.
