Admin: New server guide

2026-04-14T20:01:48Z

New server guide

New page

Did you know that the speed of your server's storage can significantly impact application performance? Optimizing your SSD (Solid State Drive) and NVMe (Non-Volatile Memory Express) drives on Linux is crucial for ensuring fast and responsive server operations. This guide will walk you through essential optimization techniques, including TRIM, I/O schedulers, filesystem mount options, and benchmarking.

== Prerequisites ==

Before you begin, ensure you have the following:

* A Linux server with SSD or NVMe storage.
* Root or sudo privileges to execute commands.
* Basic understanding of the Linux command line.
* SSH access to your server.

== Understanding SSD and NVMe Storage ==

SSDs and NVMe drives are much faster than traditional Hard Disk Drives (HDDs) because they have no moving parts. Instead, they use flash memory to store data. NVMe is a newer protocol designed specifically for SSDs, offering even lower latency and higher throughput than older SATA interfaces.

== Enabling TRIM ==

TRIM is a command that allows the operating system to inform an SSD which data blocks are no longer in use and can be wiped. This helps maintain write performance over time by preventing the drive from having to perform read-modify-write operations on blocks that are technically empty but still contain stale data.

=== Checking TRIM Status ===

First, check if TRIM is already enabled. Most modern Linux distributions enable `fstrim` via a systemd timer.

<pre>systemctl status fstrim.timer</pre>

If it's active and enabled, TRIM is likely running automatically. If not, you can enable and start it:

<pre>sudo systemctl enable fstrim.timer
sudo systemctl start fstrim.timer</pre>

You can also manually run TRIM on a specific filesystem:

<pre>sudo fstrim -v /</pre>

Replace `/` with the mount point of the filesystem you want to trim.

== Choosing an I/O Scheduler ==

An I/O scheduler is a kernel component that decides the order in which read and write requests are sent to the storage device. For SSDs and NVMe drives, the `none` or `mq-deadline` schedulers are generally recommended over traditional schedulers like `cfq` or `deadline` which were designed for HDDs.

=== Identifying Your Current I/O Scheduler ===

You can check the current I/O scheduler for your storage device. First, identify your disk:

<pre>lsblk</pre>

Look for your SSD or NVMe drive (e.g., `sda`, `nvme0n1`). Then, check its scheduler:

<pre>cat /sys/block/sda/queue/scheduler</pre>

Replace `sda` with your actual disk identifier.

=== Changing the I/O Scheduler ===

To change the scheduler temporarily (it will revert after reboot), use:

<pre>echo none | sudo tee /sys/block/sda/queue/scheduler</pre>

For a permanent change, you'll need to add a kernel parameter to your bootloader configuration (e.g., GRUB). Edit `/etc/default/grub` and add `elevator=none` to the `GRUB_CMDLINE_LINUX_DEFAULT` line. Then update GRUB:

<pre>sudo update-grub</pre>

Reboot your server for the changes to take effect.

== Filesystem Mount Options ==

Specific mount options for your filesystem can also improve performance. For ext4, the `noatime` option is commonly used. `atime` (access time) is updated every time a file is read. Disabling it can reduce disk writes, especially for read-heavy workloads.

=== Modifying /etc/fstab ===

Edit your `/etc/fstab` file to make mount options permanent.

<pre>sudo nano /etc/fstab</pre>

Find the line corresponding to your root filesystem (or other relevant filesystems) and add `noatime` to the options column. For example, a line might change from:

`UUID=... / ext4 defaults 0 1`

to:

`UUID=... / ext4 defaults,noatime 0 1`

Always back up `/etc/fstab` before editing:

<pre>sudo cp /etc/fstab /etc/fstab.bak</pre>

After saving the changes, you can either reboot or remount the filesystem:

<pre>sudo mount -o remount /</pre>

== Benchmarking Your Storage ==

Benchmarking helps you measure your storage performance before and after optimization, and to identify potential bottlenecks. `fio` (Flexible I/O Tester) is a powerful tool for this.

=== Installing fio ===

<pre>sudo apt update && sudo apt install fio -y</pre>
(For Debian/Ubuntu-based systems. Use `yum install fio` or `dnf install fio` for RHEL/CentOS/Fedora.)

=== Running a Basic Benchmark ===

Here's a simple test to measure sequential read and write speeds:

<pre>sudo fio --name=sequential_test --ioengine=libaio --rw=read --bs=1M --count=1024 --direct=1 --size=1G --directory=/tmp --numjobs=4 --runtime=60 --group_reporting</pre>

<pre>sudo fio --name=sequential_test --ioengine=libaio --rw=write --bs=1M --count=1024 --direct=1 --size=1G --directory=/tmp --numjobs=4 --runtime=60 --group_reporting</pre>

These commands will perform 1GB of sequential reads and writes from/to the `/tmp` directory using 1MB block sizes and 4 parallel jobs. Adjust parameters like `bs` (block size), `count`, `size`, and `numjobs` to simulate your specific workload.

For random I/O, change `--rw=read` to `--rw=randread` and `--rw=write` to `--rw=randwrite`.

== Troubleshooting ==

* **Performance Degradation After Changes:** If you notice a performance drop after applying optimizations, revert the changes one by one to identify the culprit. Sometimes specific hardware or workloads react differently to certain settings.
* **`fstrim` Errors:** If `fstrim` reports errors, check your drive's documentation or SMART status for potential hardware issues.
* **Boot Issues After `fstab` Edit:** If your server fails to boot after editing `/etc/fstab`, boot into a recovery mode or use a live CD/USB to restore your `/etc/fstab.bak` backup.

== Conclusion ==

Optimizing your SSD and NVMe storage with TRIM, appropriate I/O schedulers, and filesystem mount options can lead to a noticeable improvement in your Linux server's responsiveness. Regular benchmarking will help you monitor performance and ensure your optimizations are effective.

[[Category:Optimization]]
[[Category:Linux]]
[[Category:Storage]]
[[Category:Server Administration]]

SSD and NVMe Optimization for Linux - Revision history

Admin: New server guide