there's no way that the performance setting is running cooler than ondemand...
Since LNL posted the descriptions, let's recap:
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
I can see how this would cause less problems b/c, in the end, you're going all out, and you're not looking around to see what is running - which means trying to split your CPU cycles between what is there and demanding attention and what the kernel is asking for (in terms of CPU Load).
In terms of my CPU in my computer, I have it running the same way. I have mine OC'd from 2.4 to 3.2 GHz, and it is like that whenever the computer is on - No SpeedStep, No C1E Halt commands, no scaling,nothing - it goes 3.2 all the time.
for a 33% OC, you'd think my temps would be sky high, right? Feh.
I haven't broken 55 degrees C on a full load of all 4 cores using OCCT no Prim95 multithreaded. Ever.
I tried enabling C1E in my BIOS before, and I was getting temps spiking up to 62 degrees C on cores 1 and 4, oddly enough - could never figure that out.
Real world experience. Can't shake a stick at it.
Also, just because the CPU is ramped up to max speed doesn't mean it is going to produce excessive heat all the time - if nothing is using CPU cycles, it is going to be effectively doing nothing but killing the battery, waiting for something to be thrown at it so it can sink its fangs in and process.
Upvote
0