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.
Bug 1028122 - Improve the responsiveness of tuned-adm
Summary: Improve the responsiveness of tuned-adm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 17:29 UTC by Jaroslav Škarvada
Modified: 2022-09-05 09:10 UTC (History)
5 users (show)

Fixed In Version: tuned-2.3.0-2.el7
Doc Type: Bug Fix
Doc Text:
Cause: The recent tuned and python update fixed the bug that tuned was waking up the system each 50 milliseconds. As a consequence the tuned started to wake the system only after 10 seconds. This improved the power consumption but made the responsiveness of tuned worse. Consequence: Tuned could react to commands in up to 10 seconds. Fix: The main thread code was slightly reworked and the interval lowered to 1 second. Result: Tuned can now react to commands in up to 1 second with still slightly low overhead. In case you need even lower overhead and you don't mind to have longer response times, you can fine tune the sleep_interval settings in the global Tuned configuration file (/etc/tuned/tuned-main.conf). For details, see the manual page.
Clone Of:
Environment:
Last Closed: 2014-06-13 11:25:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Škarvada 2013-11-07 17:29:32 UTC
Description of problem:
Tuned-2.3.0 is more power efficient, because it is waking up system only once per 10 seconds instead of previous tuned which was waking up the system 20 times per second, but it's responsiveness is worse. It can react to commands in up to 10 seconds, which is not good user experience.

Version-Release number of selected component (if applicable):
tuned-2.3.0

How reproducible:
Always

Steps to Reproduce:
1. tuned-adm profile throughput-performance
2. tuned-adm profile balanced

Actual results:
Up to 10 seconds delay per command

Expected results:
Less delay

Additional info:

Comment 4 Branislav Blaškovič 2013-11-19 10:23:39 UTC
Verified

tuned-2.3.0-3.el7.noarch

:: [   PASS   ] :: Running '/usr/bin/time -f "%E" -o out tuned-adm profile balanced' (Expected 0, got 0)
0:00.88
:: [   PASS   ] :: Running 'cat out' (Expected 0, got 0)
:: [   PASS   ] :: Running 'awk -F':' '{if($2 > 1.5) exit 1;}' out' (Expected 0, got 0)
:: [   PASS   ] :: Running '/usr/bin/time -f "%E" -o out tuned-adm profile balanced' (Expected 0, got 0)
0:00.87
:: [   PASS   ] :: Running 'cat out' (Expected 0, got 0)
:: [   PASS   ] :: Running 'awk -F':' '{if($2 > 1.5) exit 1;}' out' (Expected 0, got 0)
:: [   PASS   ] :: Running '/usr/bin/time -f "%E" -o out tuned-adm profile balanced' (Expected 0, got 0)
0:00.84
:: [   PASS   ] :: Running 'cat out' (Expected 0, got 0)
:: [   PASS   ] :: Running 'awk -F':' '{if($2 > 1.5) exit 1;}' out' (Expected 0, got 0)
:: [   PASS   ] :: Running '/usr/bin/time -f "%E" -o out tuned-adm profile balanced' (Expected 0, got 0)
0:00.84
:: [   PASS   ] :: Running 'cat out' (Expected 0, got 0)
:: [   PASS   ] :: Running 'awk -F':' '{if($2 > 1.5) exit 1;}' out' (Expected 0, got 0)
:: [   PASS   ] :: Running '/usr/bin/time -f "%E" -o out tuned-adm profile balanced' (Expected 0, got 0)
0:00.84
:: [   PASS   ] :: Running 'cat out' (Expected 0, got 0)
:: [   PASS   ] :: Running 'awk -F':' '{if($2 > 1.5) exit 1;}' out' (Expected 0, got 0)

Beaker job is still running. I will provide results soon.

Comment 5 Branislav Blaškovič 2013-11-20 10:07:57 UTC
Beaker job results: https://beaker.engineering.redhat.com/jobs/546885
I've set treshold to 1.5 second. It is under 1 second but I made this decision because beaker machines are pretty unpredictable and we don't want false positives.

Comment 6 Jaroslav Škarvada 2013-11-20 10:41:50 UTC
(In reply to Branislav Blaškovič from comment #5)
> Beaker job results: https://beaker.engineering.redhat.com/jobs/546885
> I've set treshold to 1.5 second. It is under 1 second but I made this
> decision because beaker machines are pretty unpredictable and we don't want
> false positives.

It should be under 1 secs in most "sane" use cases, but e.g. during stress testing the response may take longer. On the other hand the affected tuned can response in up-to 10 seconds, so I think you can safely increase the threshold even more. By issuing e.g. 3 or more profile switch commands and waiting up to e.g. 3 seconds there is high probability that at least one of the commands will timeout with the affected tuned.

Comment 7 Ludek Smid 2014-06-13 11:25:14 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.