Difference: UnixPerformanceTips (1 vs. 3)

Revision 317 Feb 2004 - TWikiGuest

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="UnixTips"
(back to UnixTips)
>
>
META TOPICPARENT name="UnixNotes"
(back to UnixNotes)
  On a GNU/Linux system you actually perform a write operation for each read because the filesystem tracks the last access time for each file. While this is potentially useful data (e.g. HSM) in many cases it's useless and the file system runs slower as a result. There are a couple of ways to turn this off, depending on how precise control you need. On a file-by-file basis you can chattr +A file_name each file, or for the whole filesystem you can add noatime to the list of filesystem parameters in /etc/fstab. I've seen this documented in a few places, most recently http://www.linuxjournal.com//article.php?sid=5840

Revision 228 Mar 2002 - TobyCabot

Line: 1 to 1
 
META TOPICPARENT name="UnixTips"
(back to UnixTips)
Changed:
<
<
On a GNU/Linux system you actually write for each read because the filesystem tracks the last access time for each file. While this is potentially useful data (e.g. HSM) in many cases it's useless and the file system runs slower as a result. There are a couple of ways to turn this off, depending on how precise control you need. On a file-by-file basis you can chattr +A file_name each file, or for the whole filesystem you can add noatime to the list of filesystem parameters in /etc/fstab. I've seen this documented in a few places, most recently http://www.linuxjournal.com//article.php?sid=5840
>
>
On a GNU/Linux system you actually perform a write operation for each read because the filesystem tracks the last access time for each file. While this is potentially useful data (e.g. HSM) in many cases it's useless and the file system runs slower as a result. There are a couple of ways to turn this off, depending on how precise control you need. On a file-by-file basis you can chattr +A file_name each file, or for the whole filesystem you can add noatime to the list of filesystem parameters in /etc/fstab. I've seen this documented in a few places, most recently http://www.linuxjournal.com//article.php?sid=5840
  GNU/Linux: is IDE DMA turned on? Use hdparm to check.
Changed:
<
<
-- TobyCabot - 25 Feb 2002
>
>
Bonnie is a useful file system benchmark. My BonnieResults.

-- TobyCabot - 25 Feb 2002 - 28 Mar 2002

Revision 125 Feb 2002 - TobyCabot

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="UnixTips"
(back to UnixTips)

On a GNU/Linux system you actually write for each read because the filesystem tracks the last access time for each file. While this is potentially useful data (e.g. HSM) in many cases it's useless and the file system runs slower as a result. There are a couple of ways to turn this off, depending on how precise control you need. On a file-by-file basis you can chattr +A file_name each file, or for the whole filesystem you can add noatime to the list of filesystem parameters in /etc/fstab. I've seen this documented in a few places, most recently http://www.linuxjournal.com//article.php?sid=5840

GNU/Linux: is IDE DMA turned on? Use hdparm to check.

-- TobyCabot - 25 Feb 2002

View topic | History: r3 < r2 < r1 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding The Caboteria? Send feedback