[Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

[Julian Andres Klode]

@Colin: I agree with all of that.

Our kernel-side default is not powersave, but performance, across
generic and oem, at the very least:

$ grep CPU_FREQ_DEFAULT_GOV_.*=y /boot/config-5.*
/boot/config-5.4.0-26-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.4.0-42-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.6.0-1018-oem:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.6.0-1020-oem:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y

We used to set that to powersave (and ondemand on non-pstate) in
ondemand.service, but have since removed the service in groovy.

I believe the default governor kernel-side outside Ubuntu is usually
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND, which translates to ondemand pre-
pstates, and powersave on pstates (compare Fedora), whereas Enterprise
systems usually pick PERFORMANCE too (compare RHEL)

- probably because most distributions focus on normal end users and
enterprise on server and workstation. We don't have that distinction of
course, so I'm not sure what the best way out is - default to
powersave/ondemand and make server installer write performance - or vice
versa default to performance and make ubiquity configure powersave for
desktop.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+subscriptions