Hide Forgot
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:
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.
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.
(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.
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.