Sebastian, thanks for your guidance! On the laptop, this seems to have improved things a good amount. I will try to outline what I observed: - GUI setting `Performance` correctly yields `performance` from `/sys/.../scaling_governor` and seems to allow all cores to peg ~4.4GHz during a sysbench run - GUI setting 'Balanced` yields `powersave` from `/sys/.../scaling_governor` but the frequencies and benchmark results are the same as in `performance` mode *while plugged in*. On battery, there is a noticeable difference between Performance and Balanced - GUI setting 'Power Save` yields `powersave` from `/sys/.../scaling_governor` and shows a noticeable difference from Balanced and Performance, both on battery and plugged in - The GUI setting appears to correctly persist between reboots
All of that makes me think that the update is working correctly on the laptop. On the desktop, I observed the same behavior with respect to the GUI and `/sys/devices/...` output, however, the settings did not seem to have any notible affect on benchmark performance or core frequencies, or at least nowhere near as drastic as the laptop. Not sure if this is because desktops are intended to behave differently or because the specific CPU in the desktop is still too new to be supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066988 Title: Power setting in settings unrelated to actual power settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2066988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
