41 Change Proposal: Make Tuned the Default Power Profile Management Daemon (System-Wide)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Wiki - https://fedoraproject.org/wiki/Changes/TunedAsTheDefaultPowerProfileManagementDaemon
Discussion Thread -
https://discussion.fedoraproject.org/t/f41-change-proposal-make-tuned-the-default-power-profile-management-daemon-system-wide/118554

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==

This Change makes ‘tuned’ the default power profile management daemon
in Fedora Workstation, KDE Plasma, and Budgie instead of
power-profiles-daemon.

* tuned-ppd provides a drop-in replacement for power-profiles-daemon,
which allows it to be used with current desktops
* power users can customize the desktop-exposed power profiles by
editing /etc/tuned/ppd.conf

== Owner ==

* Name: [[User:smallorange| Kate Hsuan]], [[User:jskarvad | Jaroslav Škarvada]]

* Email: <hpa@xxxxxxxxxx>, <jskarvad@xxxxxxxxxx>

== Detailed Description ==

<p>
Tuned and power-profiles-daemon provide a similar function to set and
tune the power status of a system. Both of them have similar features,
if they can be integrated into one, it allows the Fedora user to have
more options for power settings of their system and benefits the
users. In this proposal, we set up tuned to the default power profile
management daemon for the GNOME in Fedora Workstation and the KDE
Plasma Spin. Tuned already provides power profiles for different use
cases. Recently, tuned released the translation API layer called
tuned-ppd which can translate the power-profiles-daemon API to tuned.
The applications that use power-profiles-daemon API can access tuned
without modifying the code. For now, the Fedora user can immediately
switch to tuned by installing the tuned-ppd package without impacting
the user experience. Therefore, tuned can be the default power profile
management daemon for Fedora.
</p>
<p>
This work would replace power-profiles-daemon with tuned. Since tuned
already provides a wide range of power profiles for different
purposes, this allows the user to have more options for configuring
the system power profile.
Tuned provides many kinds of advanced and basic profiles for different
purposes. Power-profiles-daemon provides the basic power profiles and
the profiles can be set to the system through platform_profiles, Intel
p-state and AMD p-state. That is simple and clever. However, if the
users want to ask for an advanced profile, they need to install
another power utility, such as tuned to fine-tune their system. With
tuned as the default power profile management daemon, users have a
wider range of profiles to fine-tune the system.
</p>
<p>
Tuned released a new translation API service called tuned-ppd
<ref>https://github.com/redhat-performance/tuned/tree/master/tuned/ppd</ref>.
tuned-ppd can translate the power-profiles-daemon API to the tuned API
so applications can talk with tuned without modification. Moreover,
the GUI settings, such as gnome-control-center can configure tuned
profiles through tuned-ppd. tuned-ppd also allows the user to override
the basic three power profiles, including power-saver, balanced, and
performance through the config file /etc/tuned/ppd.conf
<ref>https://github.com/redhat-performance/tuned/blob/master/tuned/ppd/ppd.conf</ref>.
If the user wants to use a customized profile, they can edit the
config file and map the custom profile to the basic three
power-profiles-daemon profile names. In this way, gnome-control-center
can keep the original design to configure the customized profile.
</p>
<p>
The work expects tuned to replace the power-profiles-daemons to offer
a wider range of power profiles to Fedora users. tuned-ppd resolved
the API translation issue so the application can access tuned service
through power-profiles-daemon API without converting to the tuned API.
Moreover, the three basic profiles can be overridden when the user
needs it for their use case. It also benefits GNOME applications that
can keep the original design and designing a new GUI tool for custom
profiles is unnecessary. Therefore, tuned can be the default power
setting service for Fedora.
</p>

== Feedback ==

'''From fedora-devel'''
<p>
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/B3UJKFOCRAY3BEEPTHVPW4RY5GFBZWHU/#B3UJKFOCRAY3BEEPTHVPW4RY5GFBZWHU
1. The dependency concern. Since tuned is written by Python, that
causes a dependency impact on Fedora installation.
2. The power-profiles-daemon API should be ported to tuned to provide
the function to the application that uses power-profiles-daemon API,
such as gnome-shell and gnome-control-center.
</p>
'''From the hardware vendor'''
<p>
Moreover, we discuss it with vendors through the mail.
1. Since tuned covers several kinds of system tuning schemes that
allow the vendor to implement their power profile for different
devices or workloads. For power-profile-daemon, it only has three
profiles to set and every detail setting should be done through the
firmware level. If tuned can replace power-profiles-daemon, they can
imagine they can develop the profile in a much more flexible manner.
</p>

'''The previous discussions'''
<p>
https://discussion.fedoraproject.org/t/f40-change-proposal-tuned-replaces-power-profiles-daemon-self-contained/94995
</p>

== Benefit to Fedora ==

<p>
<ol>
<li>Benefits the user. The user would have more options to tune their
system.</li>
<li>Benefits the maintainer. Integrate similar software into one
software to reduce the maintenance effort.</li>
</ol>
</p>

== Scope ==
* Proposal owners:

** for GNOME: update gnome-control-center weak dependency on
power-profile-daemon to tuned-ppd
** for KDE: update powerdevil weak dependency on power-profile-daemon
to tuned-ppd
** for Budgie: update budgie-control-center weak dependency on
power-profile-daemon to tuned-ppd

* Other developers:

* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <

* Policies and guidelines: N/A (not needed for this Change)


* Trademark approval: N/A (not needed for this Change)


* Alignment with the Fedora Strategy:


== Upgrade/compatibility impact ==

<p>
Since tuned-ppd provides the ppd APIs and features, there is no impact
on other applications.
</p>

== Early Testing (Optional) ==

Do you require 'QA Blueprint' support? Y/N

== How To Test ==

<ol>
<li>
Remove power-profiles-daemon.<br>
$ sudo dnf remove power-profiles-daemon
</li>
<li>Install tuned and tuned-ppd through the following command<br>
$ sudo dnf install tuned<br>
$ sudo dnf install tuned-ppd
</li>
<li>
Run gnome-control-center and switch to the power panel and then select
one of the three power profiles.
Click the top-right corner of the screen and you can see the “Power
Mode” shows the profile name that you selected previously.
</li>
<li>
Run the following command to show the active profile. Since tuned-adm
shows the tuned profile name, the profile name mapping can be found in
/etc/tuned/ppd.conf.<br>
$ tuned-adm active
</li>
</ol>

== User Experience ==
<ol>
<li>
The workstation user can set the power profile through the gnome-control-center.
</li>
<li>
The server users switch the profile through the tuned command line.
</li>
</ol>

== Dependencies ==
<p>
tuned is written by Python so it depends on python packages and its 40 packages.
</p>

== Contingency Plan ==

* Contingency mechanism:
<p>
Use the original power-profiles-daemon
</p>
* Contingency deadline:
<p>
Before F41 beta freeze.
</p>
* Blocks release?
<p>
No, tuned-ppd provides all the power-profiles-daemon APIs otherwise
the original power-profile-daemon can be used when the plan blocks the
release.
</p>

== Documentation ==
I have talked with tuned about this information.<br>
https://github.com/redhat-performance/tuned/issues/559

== Release Notes ==

* https://github.com/redhat-performance/tuned/tree/master/tuned/ppd

* https://github.com/redhat-performance/tuned/blob/master/tuned/ppd/ppd.conf



-- 
Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux