How to Boost Linux Server Performance by Tuning I/O Schedulers

To optimize Linux performance, IT teams should examine the current I/O scheduler and consider alternatives such as the deadline scheduler or Completely Fair Queuing (CFQ).

Poor performance on a Linux server is often linked to the storage channel. In older data centers with RAID arrays and Ext2 partitions the analysis was straightforward, but modern environments make it more complex.

Many contemporary data‑center Linux servers run atop a VMware hypervisor and connect to various Storage Area Network (SAN) systems, introducing many variables into storage optimization.

Although it is commonly believed that no storage tuning is needed on virtual machines, the Linux I/O scheduler can have a decisive impact on performance.

Understanding Different Linux I/O Scheduler Types

The I/O scheduler is a kernel component that determines how I/O requests are ordered. Common types include deadline, Completely Fair Queuing, noop, and the older anticipatory scheduler.

Most systems default to CFQ, which attempts to evenly distribute read/write requests across storage channels. While safe, it may not provide the best improvement for specific workloads.

Many IT professionals find that the noop scheduler delivers the best performance when using intelligent storage, as it passes requests directly to the storage channel. In environments with virtual machines, SSDs, or SANs, noop often performs best, but for write‑heavy loads the deadline scheduler can be more beneficial.

The deadline scheduler reorders write requests efficiently, making it a good choice for servers with heavy write operations.

The anticipatory scheduler, once used in older Linux kernels, performs read‑ahead prefetching to speed up read requests.

Setting the Linux I/O Scheduler

Administrators can set the scheduler for a specific disk or for the entire server. To set it globally, edit the GRUB configuration file /etc/default/grub, add the parameter elevator=SETTING (replace SETTING with the desired scheduler), then run grub2-mkconfig -o /boot/grub2/grub.cfg and reboot.

For per‑disk configuration, write the desired scheduler to the device’s queue file, e.g., echo deadline > /sys/block/sda/queue/scheduler. Because Linux does not provide a persistent configuration for this, the command should be added to startup scripts to apply automatically.