** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification because you are a
Hello!
Regarding the comment #8, I didn't get the same positive experience on
my side. It was more closer to what is described in comment #9. See bug
1889479 for more details.
I would suggest switching back to powersave/ondemand either with a new
service or the kernel config. Having a dedicated
I've added the OEM Solutions Group team for awareness. I'm not sure what
the final fix will be since servers' and desktops'/laptops' ideal
default seem to be different, but most likely the certification tests
should be adjusted if we don't end up restoring the previous behaviour
of the
> In benchmarking we didn't observe much computational difference
between the too once the CPU is fully loaded. However, cranking up or
cranking down the load one will discover that the performance setting is
more responsive than powersave.
this is exactly the problem in production environments;
> I would suggest switching back to powersave/ondemand either with a new
service or the kernel config.
re: new service, the existing package cpufrequtils (and related package
cpufreqd) provides a configurable service to manage governor settings
(and other related settings). The old ondemand
passing intel_pstate=disable_hwp on the kernel commandline causes the
kernel to scale the Core i5-8250U down to 1.6 GHz in performance mode,
but that's still a bit off from the 900 MHz it scales down to in
powersave mode.
I believe Windows also does not run the CPUs in performance mode by
default
@colin-king @juliank
It feels to me that the oem flavour should default to
(powersave/ondemand), as it is more-or-less laptop kernel flavour.
I feel like generic kernel flavour should remain on performance.
I feel like we should have a unit, that for chassis=laptop turns on
The choice was made from running analysis on a wide range of Intel
machines, old and new. We are trying to select the optimal choice for a
wide range of CPUs for a wide range of use cases. Generally speaking,
the intel-pstate governor has deeper understanding of the processor
features and can
@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
