https://bugs.kde.org/show_bug.cgi?id=492247
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
--- Comment #3 from Nate Graham <n...@kde.org> ---
> What's the point of having an option that nobody knows what it does? What's
> the purpose?
Everybody knows *in general* what they do purely based on their names (save
energy, balance of energy savings and performance, or maximum performance).
Nobody know what *exactly* they do because the exact details are controlled by
the device's firmware, like I said. Well, I suppose the firmware engineers
know, but that doesn't help us!
> Also those profiles actually have specific definitions.
>
> https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/blob/main/src/
> ppd-profile.h
> * @PPD_PROFILE_POWER_SAVER: "power-saver", the battery saving profile
> * @PPD_PROFILE_BALANCED: balanced, the default profile
> * @PPD_PROFILE_PERFORMANCE: as fast as possible, a profile that does
> * not care about noise or battery consumption, only available
> * on some systems.
Right, these are the power profiles.
> https://wiki.archlinux.org/title/CPU_frequency_scaling#Scaling_governors:
> - performance: Run the CPU at the maximum frequency, obtained from
> /sys/devices/system/cpu/cpuX/cpufreq/scaling_max_freq.
> - powersave: Run the CPU at the minimum frequency, obtained from
> /sys/devices/system/cpu/cpuX/cpufreq/scaling_min_freq.
> - userspace: Run the CPU at user specified frequencies, configurable via
> /sys/devices/system/cpu/cpuX/cpufreq/scaling_setspeed.
> - ondemand: Scales the frequency dynamically according to current load.
> Jumps to the highest frequency and then possibly back off as the idle time
> increases.
> - conservative: Scales the frequency dynamically according to current load.
> Scales the frequency more gradually than ondemand.
> - schedutil: Scheduler-driven CPU frequency selection.
These are different, and unrelated to the power profiles feature. We can't know
whether the firmware-specific implementation of the power profiles triggers any
of these scaling governors to be used.
> Hence my suggested definitions:
>
> With performance:
> - Unchanged
> - Limited to save power
> - Boosted when needed
> - Always at maximum
>
> Also it doesn't really matter if the definition is 100% accurate for all
> hardware, more than if it is explicit on its intention.
What is it about the current descriptions that aren't obvious to you? To me,
names like "Power save", "Balanced", and "Performance" are quite clear
regarding what they'll do. Can you help me understand what the issue is here?
--
You are receiving this mail because:
You are watching all bug changes.
