** 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
