Difference between revisions of "HowTo Disable The "relatime" Method For File "atime" Updates"
(→'''atime''') |
(→'''relatime''') |
||
Line 6: | Line 6: | ||
=='''relatime'''== | =='''relatime'''== | ||
− | Relative atime ('relatime') only | + | The [http://www.kernel.org/ Linux Kernel] supports "'''Relative atime'''" ('''relatime''') updates. A "'''relatime'''" update will only updated the "'''atime'''" field if the previous "'''atime'''" is older than the "'''mtime'''" or "'''ctime'''" for the file. This technique avoid a significant number of metadata "'''atime'''" updates. It's similar to the "'''noatime'''" mount option, but useful for applications like "[http://www.mutt.org/ mutt]" that need to know when a file has been read since it was last modified. |
Revision as of 18:35, 4 August 2008
Overview
atime
The "Access time" field for a file within a given file system is know as: "atime". When a process reads a file, the "atime" field is updated with the current date/time for this access. Disabling "atime" updates using the "noatime" mount flag is probably one of the biggest performance tweak that a Linux administrator can make. An active Linux server is continually reading files which generates a significant number of "atime" updates. This translates to numerous metadata updates made to the file system by writes to the physical disk which can lead to poor I/O performance.
relatime
The Linux Kernel supports "Relative atime" (relatime) updates. A "relatime" update will only updated the "atime" field if the previous "atime" is older than the "mtime" or "ctime" for the file. This technique avoid a significant number of metadata "atime" updates. It's similar to the "noatime" mount option, but useful for applications like "mutt" that need to know when a file has been read since it was last modified.