profiles: Correct CPU governor settings
First, always prefer schedutil for balanced/powersave. On platforms
where this governor is available, this enables Energy-Aware-Scheduling
which offers the best power efficiency and performance combination.
There is absolutely no reason to use another governor by default in the
"balanced" profile on these systems, in particular.
Second, swap around "conservative" and "ondemand". "conservative" is
supposed to be lower power and higher latency. The commit that made this
change [1] tested on a single server platform (10 years ago), but came
to the wrong conclusion. Dividing the throughput by power numbers of
that commit, "conservative" did in fact provide better performance/watt,
which is the intent of lower-power modes. The fact that it also
happened to provide better overall performance than "ondemand" is
probably an artifact of suboptimal power-management behavior or a
flawed test.
[1] b2897d9c1c
Signed-off-by: Hector Martin <marcan@marcan.st>
This commit is contained in:
parent
7480983aed
commit
e24bfef651
2 changed files with 2 additions and 2 deletions
|
|
@ -10,7 +10,7 @@ cpufreq_conservative=+r
|
|||
|
||||
[cpu]
|
||||
priority=10
|
||||
governor=conservative|powersave
|
||||
governor=schedutil|ondemand|powersave
|
||||
energy_perf_bias=normal
|
||||
energy_performance_preference=balance_performance
|
||||
boost=1
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
summary=Optimize for low power consumption
|
||||
|
||||
[cpu]
|
||||
governor=ondemand|powersave
|
||||
governor=schedutil|conservative|powersave
|
||||
energy_perf_bias=powersave|power
|
||||
energy_performance_preference=power
|
||||
boost=0
|
||||
|
|
|
|||
Loading…
Reference in a new issue