Chapter 8. Minimizing or avoiding system slowdowns due to journaling
The order in which journal changes are written to disk might differ from the order in which they arrive. The kernel I/O system can reorder the journal changes to optimize the use of available storage space. Journal activity can result in system latency by re-ordering journal changes and committing data and metadata. As a result, journaling file systems can slow down the system.
XFS is the default file system used by RHEL 8. This is a journaling file system. An older file system called
ext2 does not use journaling. Unless your organization specifically requires journaling, consider the
ext2 file system. In many of Red Hat’s best benchmark results, the
ext2 filesystem is used. This is one of the top initial tuning recommendations.
Journaling file systems like
XFS, records the time a file was last accessed (the
atime attribute). If you need to use a journaling file system, consider disabling
8.1. Disabling atime
atime attribute increases performance and decreases power usage by limiting the number of writes to the file-system journal.
/etc/fstabfile using your chosen text editor and locate the entry for the root mount point.
/dev/mapper/rhel-root / xfs defaults…
Edit the options sections to include the terms
noatimeoption prevents access timestamps being updated when a file is read, and the
nodiratimeoption stops directory inode access times being updated.
/dev/mapper/rhel-root / xfs noatime,nodiratime…
Some applications rely on
atime being updated. Therefore, this option is reasonable only on systems where such applications are not used.
Alternatively, you can use the
relatime mount option, which ensures that the access time is only updated if the previous access time is older than the current modify time.
8.2. Additional resources