Tuning ext3 for performance without losing its data integrity potential

Ext3 as the by journaling capability enhanced successor filesystem of ext2 has quite conservative default parameters which ensure an adequate data integrity after crashes. But if you make backups and using a notebook you will maybe pay a greater attention to the read/write speed of your HDD than an exaggerated and performance wasting data integrity. In the following you can see the settings which I am using for my LUKS encrypted partitions accommodated by a LVM. You have to alter the both files below as followed:

/boot/grub/menu.lst

#[...]
title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,1)
kernel /vmlinuz-2.6.22-14-generic root=/dev/mapper/vg-starlight ro rootflags=data=writeback,nobh,commit=100 splash usbcore.autosuspend=1
initrd /initrd.img-2.6.22-14-generic
quiet


/etc/fstab

#[...]
/dev/mapper/swap none swap sw 0 0
/dev/sda2 /boot ext3 noatime,nobh,data=writeback,commit=100 1 2
/dev/mapper/vg-starlight / ext3 noatime,nobh,data=writeback,commit=100 0 1
/dev/mapper/home /home ext3 noatime,nobh,data=writeback,commit=100 0 2
/dev/mapper/tmp /tmp ext3 noatime,nobh,data=writeback,commit=100 0 0


In this way you can tune the I/O performance of ext3 partitions by

  • disabling file access time logging (noatime)

  • increasing the commit interval which is responsible for writing data on the HDD (commit) to 100 seconds

  • not attaching buffer_heads to file pagecache (nobh)

  • not preserving data ordering; so data may be written into the main file system after its metadata has been committed to the journal which is the highest throughput option (data=writeback)


Due to LVM and encryption (accomplished by cryptsetup) I operate in my /etc/fstab with mapped devices. But these mapped devices can be normal block devices (like /dev/hda2, /dev/sda1 etc.) as well. Finally you should not forget to add the corresponding parameters during the system boot-up by passing them to the kernel in /boot/grub/menu.lst.

Note:
You also may be interested in how to tune ext4 for performance or how to use a swap file instead of a swap partition.

Comments

  1. Unknown22.11.13

    Very well written, yo! This the 3rd Patterns and Paradigms article I have read today, and I am pleased to see such complete and concise explanations...without all the bs. Pleased to see; OHIO, US.

    ReplyDelete

Post a Comment

Popular posts from this blog

Apple's evaluating a new JVM

To boost the Java performance on x64 Mac systems, Apple is evaluating a new Java VM  that is derived the BSD port. You can try the new JVM using the  -XXaltjvm=bsdserver VM args which is available in the recent JDK/JRE developer preview. Using this new VM may improve the Java performance and increase benchmark scores but performance drawbacks can be expected as well.
Read more

Tuning ext4 for performance with emphasis on SSD usage

The obligatory disclaimer: The more performance you gain, the more data integrity you loose! But if you want to tune something like a file system, I strongly assume that you know what you are doing :) These tips apply to all major Linux distributions like Fedora/Red Hat, OpenSUSE, and Ubuntu that are already using ext4 or are going to make ext4 their default file system. As write operations on Solid State Disks (SSD) are expensive the tips below are focused on SSD usage but also apply to HDD usage as well . My Ubuntu 9.04 Jaunty /etc/fstab after a fresh installation: [...] UUID=d818ddf9-ff01-e21a-a67d-3ceab43a9e2b / ext4 relatime,errors=remount-ro 0 1 UUID=0d339122-74e0-e0ea-805a-7879b1fa3172 /home ext4 relatime 0 2 [...] My tuned Ubuntu 9.04 Jaunty /etc/fstab : [...] UUID=d818ddf9-ff01-e21a-a67d-3ceab43a9e2b / ext4 noatime,barrier=0,nobh,commit=100,nouser_xattr 0 1 UUID=0d339122-74e0-e0ea-805a-7879b1fa3172 /home ext4 noatime,barrier=0,data=writeback,nobh,commit=100,nouser_xattr 0 2...
Read more