Home -> Mailing Lists -> Oracle-L -> Re: Tuned service on Linux

Re: Tuned service on Linux

From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Sat, 10 Feb 2024 16:21:09 -0600
Message-Id: <7F1A450C-4048-4AA8-9392-DC27F2CD05C7_at_gmail.com> 




I haven’t gone to the trouble of benchmarking, but I consider it a useful way to make sure all the environments are set up consistently.  



Sent from my iPad

On Feb 10, 2024, at 12:37, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:


I have been using the "tuned" service since its inception in the late versions of OL7. The service is up:

[oracle_at_ora21c tuned]$ systemctl status tuned
● tuned.service - Dynamic System Tuning Daemon
   Loaded: loaded (/usr/lib/systemd/system/tuned.service; enabled; vendor prese>
   Active: active (running) since Sat 2024-02-10 13:15:06 EST; 3min 37s ago
     Docs: man:tuned(8)
           man:tuned.conf(5)
           man:tuned-adm(8)
 Main PID: 1056 (tuned)
    Tasks: 6 (limit: 100264)
   Memory: 19.2M
   CGroup: /system.slice/tuned.service
           └─1056 /usr/libexec/platform-python -Es /usr/sbin/tuned -l -P

Feb 10 13:15:05 ora21c.home.com systemd[1]: Starting Dynamic System Tuning Daemon
Feb 10 13:15:06 ora21c.home.com systemd[1]: Started Dynamic System Tuning Daemon

I also make sure that the oracle plugin is installed and turned into the active profile:

[oracle_at_ora21c tuned]$ tuned-adm active
Current active profile: oracle

When I check the log, it changes a lot of parameters:

parameter 'vm.dirty_ratio' from '40' to '10'
2024-02-10 13:15:06,175 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'vm.dirty_background_ratio' from '3' to '5'
2024-02-10 13:15:06,175 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'vm.dirty_ratio' from '40' to '10'
2024-02-10 13:15:06,176 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'net.ipv4.ip_local_port_range' from '9000 65499' to '9000 65500'
2024-02-10 13:15:06,194 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'vm.dirty_background_ratio' from '3' to '5'
2024-02-10 13:15:06,194 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'vm.dirty_ratio' from '40' to '10'
2024-02-10 13:15:06,199 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'net.ipv4.ip_local_port_range' from '9000 65499' to '9000 65500'
2024-02-10 13:15:06,218 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'vm.dirty_background_ratio' from '3' to '5'
2024-02-10 13:15:06,218 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'vm.dirty_ratio' from '40' to '10'
2024-02-10 13:15:06,219 INFO     tuned.plugins.plugin_sysctl: Overriding sysctl parameter 'net.ipv4.ip_local_port_range' from '9000 65499' to '9000 65500'
2024-02-10 13:15:06,300 INFO     tuned.plugins.plugin_vm: transparent_hugepage is already set in kernel boot cmdline, ignoring value from profile
2024-02-10 13:15:06,300 INFO     tuned.daemon.daemon: static tuning from profile 'oracle' applied

However, I don't see any particular benefits from it. Can anyone share any benefits realized by setting this "tuned" thingy up? Is that just another religious ritual we perform in vain hope that the applications running on that database will run faster? I guess that the only way would be to run SLOB with and without the "tuned" service but I am too lazy for that right now.

-- 
Mladen Gogala
Database SME





--
http://www.freelists.org/webpage/oracle-l


Received on Sat Feb 10 2024 - 23:21:09 CET












Original text of this message