2016-08-27, 12:21
What is your default governor in #0826, is it "ondemand" or "performance", or something else? Check with "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor".
It should be "ondemand", but my Revo (Atom D525) is using "performance" even though the default governor is configured as "ondemand". A Skylake-based NUC uses exclusively P-States rather than "schedutil" (when enabled) and enabling "schedutil" support should have no effect on more recent Intel hardware (as it will be ignored).
So if your hardware supports P-States then you'll use P-States as your governor. Otherwise your hardware will use CPUFreq "schedutil".
You can always change the governor by writing a value ("ondemand", "performance", "powersave") to "/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor", eg. "echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor". This could be added in autostart.sh if you prefer that governor, although if schedutil is resulting in more sluggish performance then we can consider dropping it (though in theory, this shouldn't be the case).
It should be "ondemand", but my Revo (Atom D525) is using "performance" even though the default governor is configured as "ondemand". A Skylake-based NUC uses exclusively P-States rather than "schedutil" (when enabled) and enabling "schedutil" support should have no effect on more recent Intel hardware (as it will be ignored).
So if your hardware supports P-States then you'll use P-States as your governor. Otherwise your hardware will use CPUFreq "schedutil".
You can always change the governor by writing a value ("ondemand", "performance", "powersave") to "/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor", eg. "echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor". This could be added in autostart.sh if you prefer that governor, although if schedutil is resulting in more sluggish performance then we can consider dropping it (though in theory, this shouldn't be the case).
