Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I would like to revisit the rules for setting a "balanced" tuned profile. The current rules are described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1565598#c52
=======================================================
The balanced profile is used only if
* syspurpose is desktop or workstation
* chassis type is notebook, laptop, or portable
=======================================================
According to these rules, if syspurpose is not defined (empty), the profile is set to throughput-performance regardless of "chassis type".
I think that rules should be enhanced, so that if syspurpose is empty/not defined and chassis type is notebook, laptop or portable, the profile will be set to balanced.
This is what most customers would expect when installing RHEL on a portable device.
Proposed new rules:
=======================================================
The balanced profile is used only if
* syspurpose is desktop or workstation or empty/not defined
* chassis type is notebook, laptop, or portable
=======================================================
Example: for the following configuration
$ dmidecode --string chassis-type
Notebook
$ syspurpose show
{}
the tuned profile will be set to "balanced" by default.
Please let me know what you think about this proposal.
Thanks
Jirka
Comment 1Jaroslav Škarvada
2021-02-05 13:20:12 UTC
(In reply to Jiri Hladky from comment #0)
> Description of problem:
>
> I would like to revisit the rules for setting a "balanced" tuned profile.
> The current rules are described here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1565598#c52
>
> =======================================================
> The balanced profile is used only if
> * syspurpose is desktop or workstation
> * chassis type is notebook, laptop, or portable
> =======================================================
>
> According to these rules, if syspurpose is not defined (empty), the profile
> is set to throughput-performance regardless of "chassis type".
>
> I think that rules should be enhanced, so that if syspurpose is empty/not
> defined and chassis type is notebook, laptop or portable, the profile will
> be set to balanced.
>
> This is what most customers would expect when installing RHEL on a portable
> device.
>
> Proposed new rules:
> =======================================================
> The balanced profile is used only if
> * syspurpose is desktop or workstation or empty/not defined
> * chassis type is notebook, laptop, or portable
> =======================================================
>
> Example: for the following configuration
>
> $ dmidecode --string chassis-type
> Notebook
>
> $ syspurpose show
> {}
>
> the tuned profile will be set to "balanced" by default.
>
>
> Please let me know what you think about this proposal.
>
> Thanks
> Jirka
Thanks for the report, it makes sense. We will try to address it to RHEL-8.5.0.
Comment 3Jaroslav Škarvada
2021-02-05 13:44:33 UTC
(In reply to Jiri Hladky from comment #2)
> Thank you, Jaroslav!
>
> Could you please use the same rules for RHEL-9 as well?
>
> Tracking BZ for RHEL-9:
> https://bugzilla.redhat.com/show_bug.cgi?id=1921016
OK, it would get to RHEL-9 by rebase, but tracking bugzilla is better to track the progress.
Comment 10RHEL Program Management
2022-05-11 07:27:34 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Hi,
I tested the new build of tuned on the t460p laptop in our lab and the result is now correct:
$ tuned-adm active
Current active profile: balanced
Output from the support commands are:
$ dmidecode --string chassis-type
Notebook
$ syspurpose show
The 'syspurpose' command is deprecated and will be removed in a future major release. Please use the 'subscription-manager syspurpose' command going forward.
{}
Comment 21Jaroslav Škarvada
2022-08-23 09:18:00 UTC
(In reply to Jiří Vozár from comment #20)
> $ syspurpose show
> The 'syspurpose' command is deprecated and will be removed in a future major
> release. Please use the 'subscription-manager syspurpose' command going
> forward.
> {}
AFAIK in the TuneD code we use python syspurpose API, thus IMHO this shouldn't be affected.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (tuned bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7747