Notice: Check Your Tuned Settings For A Performance Boost.

Home » CentOS » Notice: Check Your Tuned Settings For A Performance Boost.
CentOS 10 Comments

Last week we noticed that the default scheduler isn’t being set properly in CentOS 7. I haven’t checked this for CentOS 6, but it might be worth exploring.

The TL;DR is unless you’re running CentOS 7 on a laptop or as a virtual guest, you should probably run

'tuned-adm profile throughput-performance'

I wrote up the full details here ->

10 thoughts on - Notice: Check Your Tuned Settings For A Performance Boost.

  • Cool. thanks!

    I have noticed (without being quite sure what to do about it) that my CentOS 7 desktop (six core AMD Vishera) seems sluggish at times, when there doesn’t seem to be much running that should be a system hog. I’ll see if this change helps resolve that.

    Does running the command shown there make a permanent change, i.e., one that survives reboot?

  • Yes. This command will drop an ‘active-profile’ file in /etc/tuned that will be used and survive reboots, kernel updates, etc.

  • [root@mutt frankcox]# tuned-adm active Current active profile: virtual-guest


    This is my main desktop computer and it isn’t any kind of a virtual system. I do run VirtualBox on it occasionally, though.

    What could have happened here?

  • On my CentOS 6 system, tuned wasn’t installed by default, but when I
    installed it and followed your instructions, that did seem to improve some programs’ performance considerably.

  • Jim Perrin wrote:

    Thank you very much for the notice! Looking at a couple machines, I found that the automatic choice of profile isn´t what I would want.

    Now I wonder how everyone deals with this, i. e. do you set a profile once and never change it, or do you keep changing the profile according to circumstances? Is changing it even advisable, i. e. do all the settings applied through a profile always take effect immediately, or may a reboot be required for some of them?

    For example, ‘virtual-host’ is a good choice during the day when the server is being used while ‘balanced’ — or even ‘powersave’ — could be used at night when the server is idle.

    I made entries in the crontab for this to change the profile at the appropriate times. But is that a good idea?

  • The change is immediate, however some processes may need to be restarted.

    Not really. Ultimately this is what the scheduler itself is meant to be doing. What you’ve described is what the ‘balanced’ profile actually does.

    For server users, I’d say it’s a set it and forget it thing.

    Laptop users who want performance when plugged in on AC, and powersave when on battery… Those are the people who should be using something like tlp or powertop (both in EPEL I think) to change this automatically.

    Jim Perrin The CentOS Project | twitter: @BitIntegrity | GPG Key: FA09AD77

  • Jim Perrin writes:

    Hmm, after looking into it a bit, I think that´s probably the idea. Alas, it doesn´t work that way *unless* the admin does look into it and creates a profile suited to each particluar machine.

    Like I´m basically ok with the ‘throughput-performance’ and
    ‘virtual-host’ profiles except for using the performance governor. That only makes sense, if at all, during the day when the servers are being used and no sense at all during the nights when they are idle. So I
    need to make my own profiles which use the conservative governor.

    But: I´m not sufficiently familiar with all the available tuning options to really make good decisions. The ‘throughput-performance’
    profile uses:

    governor=performance energy_perf_bias=performance min_perf_pct=100

    Does it even make sense to just change the governor to conservative, or does that conflict with other settings? I don´t know what the other two mean, and I think it would be stupid to run all CPUs at full throttle all the time. These servers idle a lot and can´t be fast enough when they are supposed to do something.

    BTW, what is the dynamic adjustment of tuned supposed to do? Why is tuned enabled as a daemon that does nothing because dynamic tuning is disabled?

    “Didn’t work” is an error.