Three Simple Tweaks for Better SSD Performance

Productivity Sauce
As I explained in the previous post, replacing my notebook's hard disk with an SSD significantly improved the overall system performance -- even without any additional tweaking. But there are also a couple of simple tricks that can boost performance even further. The first one is to disable the sreadahead service. The sreadahead tool helps to speed up the boot process with conventional hard disks, but it actually slows the boot with SSDs. To disable the service, open the sreadahead.conf file for editing using your preferred text editor:
sudo nano /etc/init/sreadahead.conf
Comment then the following line:
exec /sbin/sreadahead -t 0
Next trick is to add the elevator=noop kernel boot parameter to disable the elevator scheduler. On Ubuntu 9.10, open the grub.cfg file for editing:
sudo nano /boot/grub/grub.cfg
Add then the elevator=noop parameter as follows:
linux /boot/vmlinuz-2.6.31-15-generic root=UUID=b5c7bed7-58f1-4d03-88f4-15db4e367fa0 ro quiet splash elevator=noop
This scheduler is used to read and write data from the hard disk sequentially. Since an SSD is not a conventional hard disk, disabling the elevator scheduler significantly improves the read and write performance of your SSD.
Finally, you might want to set the file system mount option to noatime. To do this, edit the /etc/fstab file, so it looks something like this:
/dev/sda1 / ext4 noatime,errors=remount-ro 0 1
Adding the noatime option eliminates the need for the system to make writes to the file system for files which are simply being read -- or in other words, this means faster file access and less disk wear.
That's it. Now reboot your machine, and you should notice faster boot and better performance.
Comments
comments powered by DisqusSubscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
OpenMandriva Lx 6.0 Available for Installation
The latest release of OpenMandriva has arrived with a new kernel, an updated Plasma desktop, and a server edition.
-
TrueNAS 25.04 Arrives with Thousands of Changes
One of the most popular Linux-based NAS solutions has rolled out the latest edition, based on Ubuntu 25.04.
-
Fedora 42 Available with Two New Spins
The latest release from the Fedora Project includes the usual updates, a new kernel, an official KDE Plasma spin, and a new System76 spin.
-
So Long, ArcoLinux
The ArcoLinux distribution is the latest Linux distribution to shut down.
-
What Open Source Pros Look for in a Job Role
Learn what professionals in technical and non-technical roles say is most important when seeking a new position.
-
Asahi Linux Runs into Issues with M4 Support
Due to Apple Silicon changes, the Asahi Linux project is at odds with adding support for the M4 chips.
-
Plasma 6.3.4 Now Available
Although not a major release, Plasma 6.3.4 does fix some bugs and offer a subtle change for the Plasma sidebar.
-
Linux Kernel 6.15 First Release Candidate Now Available
Linux Torvalds has announced that the release candidate for the final release of the Linux 6.15 series is now available.
-
Akamai Will Host kernel.org
The organization dedicated to cloud-based solutions has agreed to host kernel.org to deliver long-term stability for the development team.
-
Linux Kernel 6.14 Released
The latest Linux kernel has arrived with extra Rust support and more.
noatime is safe for most application
atime (access time) is updated whenever a file system object is read -- even from cache.
ctime (ionode modification time) gets updated whenever the file system object's ionode is changed (e.g., file/directory is created, ownership is changed, permissions are changed, file/directory is deleted).
mtime (object modification time) gets updated whenever the file system object is modified (e.g., truncated, appended, overwritten).
Well-written backup applications use the mtime to flag modified files for progressive, incremental, and differential backup modes. If the backup application also preserves ownership & permissions, it should also look at ctime. atime is no use whatsoever here -- backups are interested about file changes -- not reads.
atime has a few edge cases. Some systems audit file reads to track usage. tmpwatch removes aged files from the /tmp directory based on atime. mail-notify looks at atime to notify users about new mail. Cache & proxy servers once used atime for pruning objects from their cache, but this has been largely replaced by tree indices that can weigh multiple factors (e.g., number of requests vs. aging).
For the most part noatime is completely irrelevant. If in doubt, read the opinions of the holy trinity of Linux development -- Linus Torvalds, Andrew Morton, and Ingo Molnar:
http://kerneltrap.org/node/14148
noatime may break some applications like backup tools
noatime implies nodiratime
Anon
Something similar may apply to general readahead too - if you are going to need those blocks later sequential readahead can still be a win as you will simply wait less later (at a point when you would have had to stall).
sreadahead
journaling on SSD is also a bad idea
fstab
/dev/sda1 / ext4 noatime,nodiratime,errors=remount-ro 0 1
setting readahead values for just one drive
blockdev --setra 0 /dev/sda
Obviously you'll want to put this command in a init.d file or similar...
p.s. this is only for 2.6 kernels
Test results
Re: GRUB configuration changes
Re: Quality information
There are many ways to skin a cat, and I don't pretend that my way is the best one. However, I did try all the modifications myself and they worked.
You are right, though. I should have thanked you for commenting on my post. I'm always grateful to people who find time to share their ideas and knowledge with others. Thank you!
GRUB configuration changes
on Ubuntu 9.10 I recommend editing /etc/default/grub instead of /boot/grub/grub.cfg. Any changes made to /boot/grub/grub.cfg directly will be lost the next time update-grub2 is executed (like when a new kernel or kernel-patch is installed via software update). So, by changing the line
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash elevator=0"
in /etc/default/grub and then running update-grub2 one can make this change more persistent.
Juergen Pabel
Re: editing grub.cfg is not advised in Ubuntu
thanks
Quality information
You also do things in a terribly dirty way.
Learn to disable a service. Uh uninstall readahead may be even esier. That and editing grub configuration properly.
Why don't you give it some time, get some real experience and test the modifications thoroughly then start filling the web with quality information?
Also, next time at least say "thank you".
editing grub.cfg is not advised in Ubuntu
The preferred way to change boot parameters in Ubuntu 9.10 is by editing /etc/default/grub, altering the line that starts with GRUB_CMDLINE_LINUX_DEFAULT=... to suit your needs. Once you have saved it, run update-grub to apply the changes to /boot/grub/grub.cfg. Verify that the changes are in place, and then reboot.
Or, in the specific case in this article, just "echo noop > /sys/block/DEVICE/queue/scheduler" to change the elevator without rebooting, substituting the correct device name for DEVICE.