similar to: tuned profile and i/o scheduler

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 ->

On 09/21/2017 07:02 PM, Fred Smith wrote: > On Thu, Sep 21, 2017 at 11:45:12AM -0700, Jim Perrin wrote: >> 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 >>

Jim Perrin wrote: > 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

On 09/23/2017 03:52 AM, hw 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.

Hi wich tuned profile are the best for dom0 and domU? There are virt-host and virt-guest profiles for kvm, should I use them? If yes, should I use in domU ever virt-guest or is for example network-throughput profile better for a nfs/samba fs server inside domU better? -- ------ Greetz

On 7/4/19 10:18 PM, Steven Tardy wrote: > I would also look at power settings in the BIOS and c-state settings in the > BIOS and OS as disabling c-states (often enabled by default to meet > green/energy star compliance) can make a noticeable performance difference. I'd be surprised if it did, but now that you mention it, I think that we should probably mention more often that

On Thu, Sep 21, 2017 at 11:45:12AM -0700, Jim Perrin wrote: > 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

Hi, what is the point of running tuned as a daemon when dynamic tuning is disabled? What is the point of enabling dynamic tuning, especially when using the supplied profiles like throughput-performance? I haven't customized those by specifying any thresholds, and I don't see any point in doing things like dynamically changing disk schedulers or CPU governors depending on something

On a 32bit Windows 2008 Server guest VM on a CentOS 5 host, iometer reported a disk write speed of 37MB/s The same VM on a CentOS 6 host reported 0.3MB/s. i.e. The VM was unusable. Write performance in a CentOS 6 VM was also much worse, but it was usable. (See http://lists.centos.org/pipermail/centos-virt/2012-August/002961.html) With iometer still running in the guest, I installed tuned on

hi, twice in the last week I've been caught out where the laptop was running tuned with 'throughput-performance' profile on the work table, and I walked away, carried on working - and had the battery run flat in just over an hour. Compare this with tuned running the 'powersave' profile - will usually take the battery through to 3hrs+ - and if i just totally turn down the

Hi, What's the correct way to change configuration parameters for an iSCSI device? For example I/O scheduler, max_sectors_kb, etc... I could add commands to the S99local script: echo noop > /sys/block/sdb/queue/scheduler echo 64 > /sys/block/sdb/queue/max_hw_sectors_kb Unfortunately, iSCSI device names might change from sdb to, say, sdc (server reboot, iSCSI target reconnection).

This was an email I sent to xen-devel a while ago without getting a response. I''m reposting it here in case someone knows more. Hello all, I''m able to consistently reproduce lockups in my domU with heavy I/O with the following error: 36841.420662] INFO: task rsyslogd:15014 blocked for more than 120 seconds. [36841.420843] "echo 0>

On Fri, 22 Sep 2017 09:04:58 -0700 Jim Perrin wrote: > Yes. This command will drop an 'active-profile' file in /etc/tuned that > will be used and survive reboots, kernel updates, etc. [root at 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

On Fri, Sep 22, 2017 at 12:05 PM, Frank Cox <theatre at sasktel.net> wrote: > On Fri, 22 Sep 2017 09:04:58 -0700 > Jim Perrin wrote: > > > Yes. This command will drop an 'active-profile' file in /etc/tuned that > > will be used and survive reboots, kernel updates, etc. > > [root at mutt frankcox]# tuned-adm active > Current active profile: virtual-guest

Hi, I noticed on one of the discussion that both Dom0 and DomU have the same scheduler will cause I/O issues and changing the I/O scheduler to noop for Xen VPS will give better performance. Is it correct? If its correct then how can we set the default I/O scheduler as noop for Xen VM''s without getting inside of them? I mean is there any option that we can declare on DomU config itself?

Does tuned on CentOS 6.9 (i.e. tuned-0.2.19-18.el6.noarch) do any dynamic tuning, or does it only support static configuration via a static profile? Chris

CentOS Errata and Bugfix Advisory 2019:0496 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0496 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ce7752b7fd1c7b911135eaab8c195179989fe0058d0575f168ec13e9018c6239 tuned-2.10.0-6.el7_6.3.noarch.rpm

CentOS Errata and Bugfix Advisory 2019:1901 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1901 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6d0b8790381395501b1333d4a1e13849b10f10737de6d2a78f1763605e0cdd3b tuned-2.10.0-6.el7_6.4.noarch.rpm

CentOS Errata and Bugfix Advisory 2019:2605 Upstream details at : https://access.redhat.com/errata/RHBA-2019:2605 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 35dbeac8128a78150bf3d0546116edbad238e4e09cb8dafd070405a513562a15 tuned-2.11.0-5.el7_7.1.noarch.rpm

CentOS Errata and Bugfix Advisory 2020:5008 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5008 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 314863a27a19049fe9480f37f1d931ad115a3966777cfe9685ce45f0eaf763a2 tuned-2.11.0-10.el7.noarch.rpm