Difference between revisions of "Improving performance"

From ArchWiki
Jump to navigation Jump to search
(use HTTPS; added AUR templates; flagged CPU section as out of date; minor rewrites)
(BTRFS: upstream seems to prefer "Btrfs" over "BTRFS")
Line 99: Line 99:
Replace /dev/hda1 with the partition reserved for the journal, and /dev/hdb1 with the partition for data.  You can learn more about reiserfs with this [http://www.funtoo.org/en/articles/linux/ffg/2/ article].
Replace /dev/hda1 with the partition reserved for the journal, and /dev/hdb1 with the partition for data.  You can learn more about reiserfs with this [http://www.funtoo.org/en/articles/linux/ffg/2/ article].
See [[Btrfs#Defragmentation|defragmentation]] and [[Btrfs#Compression|compression]].
See [[Btrfs#Defragmentation|defragmentation]] and [[Btrfs#Compression|compression]].

Revision as of 00:37, 7 July 2012

zh-CN:Maximizing Performance This article is a retrospective analysis and basic rundown about gaining performance in Arch Linux.

The basics

Know your system

The best way to tune a system is to target the bottlenecks, that is the subsystems that limit the overall speed. They usually can be identified by knowing the specifications of the system, but there are some basic indications:

  • If the computer becomes slow when big applications, like OpenOffice.org and Firefox, are running at the same time, then there is a good chance the amount of RAM is insufficient. To verify available RAM, use this command, and check for the line beginning with -/+buffers:
$ free -m
  • If boot time is really slow, and if applications take a lot of time to load the first time they are launched, but run fine afterwards, then the hard drive is probably too slow. The speed of a hard drive can be measured using the hdparm command:
$ hdparm -t /dev/harddrive

This is only the pure read speed of the hard drive, and is not a valid benchmark, but a value superior to 40MB/s (assuming drive tested while idle) can be considered decent on an average system.

  • If the CPU load is consistently high even when RAM is available, then lowering CPU usage should be a priority. CPU load can be monitored in many ways, like using the top command:
$ top
  • If the only applications lagging are the ones using direct rendering, meaning they use the graphic card, like video players and games, then improving the graphic performance should help. First step would be to verify if direct rendering simply is not enabled. This is indicated by the glxinfo command:
$ glxinfo | grep direct

The first thing to do

The simplest and most efficient way of improving overall performance is to run lightweight environments and applications.


Almost all tuning brings drawbacks. Lighter applications usually come with less features and some tweaks may make a system unstable, or simply require time to implement and maintain. This page tries to highlight those drawbacks, but the final judgment rests on the user.


The effects of optimization are often difficult to judge. They can however be measured by benchmarking tools

Storage devices

Device Layout

One of the the biggest performance gains comes from having multiple storage devices in a layout that spreads the operating system work around. Having / /home /var /usr /lib on separate disks is dramatically faster than a single disk layout where they are all on the same hard drive.

Swap Files

Creating your swap files on a separate disk can also help quite a bit, especially if your machine swaps frequently or you have less than 8G of RAM.

RAID Benefits

If you have multiple disks (2 or more) available, you can set them up as a software RAID for serious speed improvements. In a RAID 0 array there is no redundancy in case of drive failure, but for each additional disk you add to the array, the speed of the disk becomes that much faster. The smart choice is to use RAID 5 which offers both speed and data protection.

Multiple Hardware Paths

An internal hardware path is how the storage device is connected to your motherboard. There are different ways to connect to the motherboard such as TCP/IP through a NIC, plugged in directly using PCIe/PCI, Firewire, Raid Card, USB, etc. By spreading your storage devices across these multiple connection points you maximize the capabilities of your motherboard, for example 6 hard-drives connected via USB would be much much slower than 3 over USB and 3 over Firewire. The reason is that each entry path into the motherboard is like a pipe, and there is a set limit to how much can go through that pipe at any one time.. the good news is that the motherboard usually has several pipes.

More Examples

  1. Directly to the motherboard using pci/PCIe/ata
  2. Using an external enclosure to house the disk over USB/Firewire
  3. Turn the device into a network storage device by connecting over tcp/ip

Note also that if you have a 2 USB ports on the front of your machine, and 4 USB ports on the back, and you have 4 disks, it would probably be fastest to put 2 on front/2 on back or 3 on back/1 on front. This is because internally the front ports are likely a separate Root Hub than the back, meaning you can send twice as much data by using both than just 1. Use the following commands to determine the various paths on your machine.

USB Device Tree
$ lsusb -t
PCI Device Tree
$ lspci -t


The partition layout can influence the system's performance. Sectors at the beginning of the drive (closer to the center of the disk) are faster than those at the end. Also, a smaller partition requires less movements from the drive's head, and so speed up disk operations. Therefore, it is advised to create a small partition (10gb, more or less depending on your needs) only for your system, as near to the beginning of the drive as possible. Other data (pictures, videos) should be kept on a separate partition, and this is usually achieved by separating the home directory (/home/user) from the system (/).

Choosing and tuning your filesystem

Choosing the best filesystem for a specific system is very important because each has its own strengths. The beginner's guide provides a short summary of the most popular ones. You can also find relevant articles here.


  • XFS: Excellent performance with large files. Low speed with small files. A good choice for /home.
  • Reiserfs: Excellent performance with small files. A good choice for /var.
  • Ext3: Average performance, reliable.
  • Ext4: Great overall performance, reliable, has performance issues with sqlite and some other databases.
  • JFS: Good overall performance, very low CPU usage, extremely fast resume after power failure.
  • Btrfs: Probably best overall performance (with compression) and lots of features. Still in heavy development and fully supported, but considered as unstable. Do not use this filesystem yet unless you know what you are doing and are prepared for potential data loss.

Mount options

Mount options offer an easy way to improve speed without reformatting. They can be set using the mount command:

$ mount -o option1,option2 /dev/partition /mnt/partition

To set them permanently, you can modify /etc/fstab to make the relevant line look like this:

/dev/partition /mnt/partition partitiontype option1,option2 0 0

The mount options noatime,nodiratime are known for improving performance on almost all file-systems. The former is a superset of the latter (which applies to directories only -- noatime applies to both files and directories). In rare cases, for example if you use mutt, it can cause minor problems. You can instead use the relatime option (NB relatime is the default in >2.6.30)


See Ext3.


See Ext4.


See JFS Filesystem.


For optimal speed, create an XFS file-system with:

$ mkfs.xfs -l internal,lazy-count=1,size=128m -d agcount=2 /dev/thetargetpartition


The data=writeback mount option improves speed, but may corrupt data during power loss. The notail mount option increases the space used by the filesystem by about 5%, but also improves overall speed. You can also reduce disk load by putting the journal and data on separate drives. This is done when creating the filesystem:

$ mkreiserfs –j /dev/hda1 /dev/hdb1

Replace /dev/hda1 with the partition reserved for the journal, and /dev/hdb1 with the partition for data. You can learn more about reiserfs with this article.


See defragmentation and compression.

Compressing /usr

Note: As of version 3.0 of the linux kernel aufs2 is no longer supported.

A way to speed up reading from the hard drive is to compress the data, because there is less data to be read. It must however be decompressed, which means a greater CPU load. Some filesystems support transparent compression, most notably btrfs and reiserfs4, but their compression ratio is limited by the 4k block size. A good alternative is to compress /usr in a squashfs file, with a 64k(128k) block size, as instructed in this Gentoo forums thread. What this tutorial does is basically to compress the /usr folder into a compressed squashfs file-system, then mounts it with aufs. A lot of space is saved, usually two thirds of the original size of /usr, and applications load faster. However, each time an application is installed or reinstalled, it is written uncompressed, so /usr must be re-compressed periodically. Squashfs is already in the kernel, and aufs2 is in the official repositories, so no kernel compilation is needed if using the stock kernel. Since the linked guide is for Gentoo, the next commands outline the steps specifically for Arch. To get it working, install the packages aufs2 and squashfs-tools. These packages provide the aufs-modules and some userspace-tools for the squash-filesystem.

Now we need some extra directories where we can store the archive of /usr as read-only and another folder where we can store the data changed after the last compression as writeable:

# mkdir -p /squashed/usr/{ro,rw}

Now that we got a rough setup you should perform a complete system-upgrade since every change of content in /usr after the compression will be excluded from this speedup. If you use prelink you should also perform a complete prelink before creating the archive. Now it is time to invoke the command to compress /usr:

# mksquashfs /usr /squashed/usr/usr.sfs -b 65536

These parameters/options are the ones suggested by the Gentoo link but there might be some room for improvement using some of the options described here. Now to get the archive mounted together with the writeable folder it is necessary to edit /etc/fstab:

# nano /etc/fstab

Add the following lines:

/squashed/usr/usr.sfs   /squashed/usr/ro   squashfs   loop,ro   0 0 
usr    /usr    aufs    udba=reval,br:/squashed/usr/rw:/squashed/usr/ro  0 0

Now you should be done and able to reboot. The original Author suggests to delete all the old content of /usr, but this might cause some problems if anything goes wrong during some later re-compression. It is more safe to leave the old files in place just to be on the safe side.

A Bash script has been created that will automate the process of re-compressing (read updating) the archive since the tutorial is meant for Gentoo and some options do not correlate to what they should be in Arch.

Tuning for an SSD


RAM disks / tuning for really slow disks


The only way to directly improve CPU speed is overclocking. As it is a complicated and risky task, it is not recommended for anyone except experts. The best way to overclock is through the BIOS. When purchasing your system, keep in mind that most Intel motherboards are notorious for disabling the capacity to overclock.

A way to modify performance (ref) is to use Con Kolivas' desktop-centric kernel patchset, which, among other things, replaces the Completely Fair Scheduler (CFS) with the Brain Fuck Scheduler (BFS).

Kernel PKGBUILDs that include the BFS patch can be installed from the AUR or Unofficial User Repositories. See the respective pages for linux-ckAUR and Linux-ck wiki page, linux-bfsAUR or linux-pfAUR for more information on their additional patches.

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: The kernel.org link is dead in the following Note box. (Discuss in Talk:Improving performance#)
Note: BFS/CK are designed for desktop/laptop use and not servers. They provide low latency and work well for 16 CPUs or less. Also, Con Kolivas suggests setting HZ to 1000. For more information, see the BFS FAQ and ck patches.


Verynice is a daemon, available in the AUR as veryniceAUR, for dynamically adjusting the nice levels of executables. The nice level represents the priority of the executable when allocating CPU resources. Simply define executables for which responsiveness is important, like X or multimedia applications, as goodexe in /etc/verynice.conf. Similarly, CPU-hungry executables running in the background, like make, can be defined as badexe. This prioritization greatly improves system responsiveness under heavy load.


Ulatencyd is a daemon that controls how the Linux kernel will spend its resources on the running processes. It uses dynamic cgroups to give the kernel hints and limitations on processes. It supports prioritizing processes for disk I/O as well as CPU shares, and uses more clever heuristics than Verynice. In addition, it comes with a good set of configs out of the box.

One note of warning, by default it changes the default scheduler of all block devices to cfq, to disable behavior see Ulatencyd.


See relevant section in General Recommendations.


Xorg.conf configuration

Graphic performance heavily depends on the settings in /etc/X11/xorg.conf. There are tutorials for Nvidia, ATI and Intel cards. Improper settings may stop Xorg from working, so caution is advised.


Driconf is a small utility that allows you to change the direct rendering settings for open source drivers. Enabling HyperZ can drastically improve performance.

GPU Overclocking

Overclocking a graphics card is typically more expedient than with a CPU, since there are readily accessible software packages which allow for on-the-fly GPU clock adjustments. For ATI users, get rovclockAUR, and Nvidia users should get nvclock in the extra repository. Intel chipsets users can install GMABooster from with the gmaboosterAUR AUR package.

The changes can be made permanent by running the appropriate command after X boots, for example by adding it to ~/.xinitrc. A safer approach would be to only apply the overclocked settings when needed.

RAM and swap

Browser profile in tmpfs

Relocate the browser profile to tmpfs file system, including /tmp, or /dev/shm for improvements in application response as the the entire profile is now stored in RAM. Another benefit is a reduction in disk read and write operations, of which SSDs benefit the most.

Use an active management script for maximal reliability and ease of use.

Refer to the Profile-sync-daemon wiki article for more.


The swappiness represent how much the kernel prefers swap to RAM. Setting it to a very low value, meaning the kernel will almost always use RAM, is known to improve responsiveness on many systems. To do that, simply add those line to /etc/sysctl.conf:


To test and more on why this may work, take a look at this article.


Compcache, nowadays replaced by the zram kernel module, creates a device in RAM and compresses it. If you use for swap means that part of the RAM can hold much more information but uses more CPU. Still, it is much quicker than swapping to a hard drive. If a system often falls back to swap, this could improve responsiveness. Zram is in mainline staging (therefore its not stable yet, use with caution). zramswapAUR package automatically sets up such swap device on every boot with optimal settings for your system (such as RAM size and CPU core number).

To manually set up a 50Mb zram swap, do the following:

 modprobe zram
 echo $((50*1024*1024)) > /sys/block/zram0/disksize
 mkswap /dev/zram0
 swapon -p 60 /dev/zram0

To make the changes permanent, add zram module to /etc/rc.conf and autostart by adding the following lines to /etc/rc.local:

 echo $((50*1024*1024)) > /sys/block/zram0/disksize
 mkswap /dev/zram0
 swapon -p 60 /dev/zram0

You will have a 50MB swap with higher priority than your regular swap which will utilize one CPU core for compessing data. See Scalability article in compcache/zram wiki for instructions for utilizing multiple cores, or simply use zramswapAUR from AUR.

systemd-arch-units provide a zram.service for Systemd. It creates one zram device per CPU/core with a total space equivalent to the RAM available. To enable it on boot, simply run:

 systemctl enable zram.service

This is also a good way to reduce disk read/write cycles due to swap on SSDs.

Using the graphic card's RAM

In the unlikely case that you have very little RAM and a surplus of video RAM, you can use the latter as swap. See Swap on video ram.


Preloading is the action of putting and keeping target files into the RAM. The benefit is that preloaded applications start more quickly because reading from the RAM is always quicker than from the hard drive. However, part of your RAM will be dedicated to this task, but no more than if you kept the application open. Therefore preloading is best used with large and often-used applications like Firefox and OpenOffice.


Go-preload is a small daemon created in the Gentoo forum. To use it, first run this command in a terminal for each program you want to preload at boot:

# gopreload-prepare program

Then, as instructed, press Enter when the program is fully loaded. This will add a list of files needed by the program in /usr/share/gopreload/enabled. To load all lists at boot, add gopreload to your DAEMONS array in /etc/rc.conf. To disable the loading of a program, remove the appropriate list in /usr/share/gopreload/enabled or move it to /usr/share/gopreload/disabled.


A more automated approach is used by Preload. All you have to do is add it to your DAEMONS array in /etc/rc.conf. It will monitor the most used files on your system, and with time build its own list of files to preload at boot.


Readahead is a tool that can cache files before they are needed and help accelerate program loading.

Boot time

You can find tutorials with good tips in the article Improve Boot Performance.

Suspend to ram

The best way to reduce boot time is not booting at all. Consider suspending your system to ram instead.

Kernel boot options

Some boot options can decrease kernel boot time. The fastboot option usually can take off one second or so (but it sacrifices checking rootfs by fsck). Also, if you see a message saying "Waiting 8s for device XXX" at boot, adding rootdelay=1 can reduce the waiting time, but be careful, as it may break the booting process. Those options are set in /boot/grub/menu.lst or /etc/lilo.conf, depending on which bootloader you use.

Custom kernel

Compiling a custom kernel will reduce boot time and memory usage, but can be long, complicated and even painful. It usually is not worth the effort, but can be very interesting and a great learning experience. If you really know what you are doing, start here.

Application-specific tips


The Firefox Tweaks article offers good tips; notably turning off anti-phishing, disabling Pango and cleaning the SQlite database. See also: Firefox in Ramdisk.

Firefox in the official repositories is built with the profile guided optimization flag enabled. You may want to use it in your custom build. To do this append

ac_add_options --enable-profile-guided-optimization

to your mozconfig.


See Ccache.


See Speed up LibreOffice.


See Improve Pacman Performance.


See Speed up SSH.


See Laptop.