Latest revision as of 08:15, 2 May 2024

Tuned Replaces Power-profiles-daemon

This is a rejected Change proposal for Fedora Linux.
This document represents a proposed Change that has been rejected or withdrawn as part of the Changes process. This page is preserved for historical record.

Summary

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 be the default power profile management daemon for the Fedora workstation, including GNOME and KDE plasma. 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.

Owner

Name: Kate Hsuan, Jaroslav Škarvada
Email: <hpa@redhat.com>, <jskarvad@redhat.com>

Current status

Targeted release: Fedora Linux 41
Last updated: 2024-05-02
Announced
Discussion thread
FESCo issue: #3103
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

This work would replace power-profiles-daemon (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. As far as we know, 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. If tuned can be the default power profile management daemon, the users would have a wide range of profiles to fine-tune the system.

Tuned released a new translation API service called tuned-ppd ^[1]. tuned-ppd can translate the power-profiles-daemon API to tuned API so the application can talk with tuned without modifying the codes. Moreover, the GUI settings, such as gnome-control-center can configure tuned profile 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 ^[2]. 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.

The work expects the tuned to replace the power-profiles-daemons to offer a wide range of power profiles to the fedora users. tuned-ppd resolved the API translation issue so the application can access tuned service through power-profiles-daemon API without converting to tuned API. Moreover, tuned allows the three profiles to be overridden with custom power profiles if the user wants to use custom profiles for the specific use cases. 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.

Feedback

From fedora-devel

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/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.

From the hardware vendor

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.

Benefit to Fedora

1. Benefits the user. The user would have more options to tune their system.

2. Benefits the maintainer. Integrate similar software into one software to reduce the maintenance effort.

Scope

Proposal owners:

Other developers:

Release engineering: #Releng issue number

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

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

Alignment with Community Initiatives:

Upgrade/compatibility impact

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

How To Test

1. Install tuned and tuned-ppd through the following command
$ sudo dnf install tuned
$ sudo dnf install tuned-ppd

2. 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 profiles name that you selected previously.

3. 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.
$ tuned-adm active

User Experience

1. The workstation user can set the power profile through the gnome-control-center.
2. The server users switch the profile through the tuend command line.

Dependencies

1. tuned is written by Python so it depends on python packages and its 40 packages.

Contingency Plan

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)

Use the original power-profiles-daemon

Contingency deadline: N/A (not a System Wide Change)

Before F41 beta freeze.

Blocks release? N/A (not a System Wide Change), Yes/No

No, tuned-ppd provides all the ppd APIs otherwise the original power-profile-daemon can be used.

Documentation

I have talked with tuned about this information. https://github.com/redhat-performance/tuned/issues/559

N/A (not a System Wide Change)

Release Notes

[1] ttps://github.com/redhat-performance/tuned/tree/master/tuned/ppd

[2] ttps://github.com/redhat-performance/tuned/blob/master/tuned/ppd/ppd.conf

[1]

[2]

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
 <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Change Proposal Name <!-- The name of your change proposal --> =
+= Tuned Replaces Power-profiles-daemon =
-{{Change_Proposal_Banner}}
+{{Change_Rejected_Banner}}
 == Summary ==
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
+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 be the default power profile management daemon for the Fedora workstation, including GNOME and KDE plasma. 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.
 == Owner ==
@@ Line 19: / Line 15: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:smallorange| Kate Hsuan]], [[User:jskarvad | Jaroslav Škarvada]]
 <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
+* Email: <hpa@redhat.com>, <jskarvad@redhat.com>
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 -->
 == Current status ==
@@ Line 35: / Line 30: @@
 <!-- Select proper category, default is Self Contained Change -->
-[[Category:SelfContainedChange]]
+[[Category:SystemWideChange]]
 <!-- [[Category:SystemWideChange]] -->
-* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f<VERSION>/ Fedora Linux <VERSION>]
+* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 46: / Line 41: @@
 ON_QA -> change is fully code complete
 -->
-* [<will be assigned by the Wrangler> devel thread]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/745KXCINZGO5EHGXEVIBE3BR26INPZCJ/ Announced]
-* FESCo issue: <will be assigned by the Wrangler>
+* [https://discussion.fedoraproject.org/t/f40-change-propsal-tuned-replaces-power-profiles-daemon-self-contained/94995 Discussion thread]
+* FESCo issue: [https://pagure.io/fesco/issue/3103 #3103]
 * Tracker bug: <will be assigned by the Wrangler>
 * Release notes tracker: <will be assigned by the Wrangler>
@@ Line 53: / Line 49: @@
 == Detailed Description ==
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+This work would replace power-profiles-daemon (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.
+As far as we know, 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. If tuned can be the default power profile management daemon, the users would have a wide range of profiles to fine-tune the system.
+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 tuned API so the application can talk with tuned without modifying the codes. Moreover, the GUI settings, such as gnome-control-center can configure tuned profile 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.
+The work expects the tuned to replace the power-profiles-daemons to offer a wide range of power profiles to the fedora users. tuned-ppd resolved the API translation issue so the application can access tuned service through power-profiles-daemon API without converting to tuned API. Moreover, tuned allows the three profiles to be overridden with custom power profiles if the user wants to use custom profiles for the specific use cases. 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.
 == Feedback ==
 <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
+'''From fedora-devel'''
+https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/B3UJKFOCRAY3BEEPTHVPW4RY5GFBZWHU/#B3UJKFOCRAY3BEEPTHVPW4RY5GFBZWHU
+. The dependency concern. Since tuned is written by Python, that causes a dependency impact on Fedora installation.
+. 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.
+'''From the hardware vendor'''
+Moreover, we discuss it with vendors through the mail.
+. 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.
 == Benefit to Fedora ==
@@ Line 85: / Line 102: @@
       https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+. Benefits the user. The user would have more options to tune their system.
+. Benefits the maintainer. Integrate similar software into one software to reduce the maintenance effort.
 == Scope ==
@@ Line 110: / Line 130: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Since tuned-ppd provides the ppd APIs and features, there is no impact on other applications.
 == How To Test ==
@@ Line 128: / Line 148: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+<p>
+. Install tuned and tuned-ppd through the following command<br>
+$ sudo dnf install tuned<br>
+$ sudo dnf install tuned-ppd
+</p>
+<p>
+. 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 profiles name that you selected previously.
+</p>
+</p>
+. 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
+</p>
 == User Experience ==
@@ Line 141: / Line 173: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+. The workstation user can set the power profile through the gnome-control-center.<br>
+. The server users switch the profile through the tuend command line.
 == Dependencies ==
@@ Line 146: / Line 181: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+. tuned is written by Python so it depends on python packages and its 40 packages.
 == Contingency Plan ==
@@ Line 152: / Line 187: @@
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 * Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Use the original power-profiles-daemon
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
 * Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Before F41 beta freeze.
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 * Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+No, tuned-ppd provides all the ppd APIs otherwise the original power-profile-daemon can be used.
 == Documentation ==
 <!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+I have talked with tuned about this information.
+https://github.com/redhat-performance/tuned/issues/559
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Search

Changes/TunedReplacesPower-profiles-daemon: Difference between revisions