Ok, and mail-notify too i guess. Out of tens of thousands of applications. But people still use some programs that need it, and removing atime would break those user programs. And the rule in Linux kernel development is not to break userspace. Linux distributions include a lot of software applications, and users can download and install other programs to suit their particular needs.
That's the key benefit of an open source operating system! But that makes things more difficult in tuning your filesystem performance. Do you need atime , or will removing it break something on your system? As a compromise, Linux kernel developers implemented a new method: relatime is a slightly different performance measure that is meant to balance performance with compatibility. The mount man page says this about relatime :.
Access time is only updated if the previous access time was earlier than the current modify or change time. In short: modern Linux systems since Linux 2. But if you're looking to tweak your system to get maximum performance, disabling atime is still a valid option in This performance tweak might not be very noticeable on very fast modern drives like NVME or a fast SSD , but there's still a little boost there. This tells the kernel not to track the Last Accessed time, avoiding that tiny performance hit to continually update atime in the filesystem.
Add noatime as an option to your Linux filesystems, usually after the defaults entry:. The biggest issue with atime is SSD write cycles. An SSD has a life that is measured in number of write cycles. With atime enabled, every read results in a write, to update the atime. When a write takes place on an SSD, a whole block must be read, changed and rewritten.
It would be nice if some kind of atime cache was implemented so file accesses wouldn't cause disk IO. ATime infomation could then be written at long intervals, and at unmount time. In any case, one could consider using the relatime flag by default to optimse disk IO performance not breaking application functionality.
Atime updates are by far the biggest IO performance deficiency that Linux has today. Noatime is good, but remember that you will not be able to know when something was last accessed, so consider your needs carefully.
Many people can do without atime, though you must be careful, as some things like backups, the popularity contest, and other things rely on it. Unfortunately, turning off atime unconditionally will occasionally break software. Some mail tools will compare modification and access times to determine whether there is unread mail or not. The tmpwatch utility and some backup tools also use atime and can misbehave if atime is not correct. Dirt Rally Driver HD. Desert Hawk. Star Defender 4.
Legends of Honor. Martian Transporter. Star Defender 3. Toy Defense 2. Sudden Strike 2. Theseus - Return of the Hero. Sky Runners. Mini Metal. Star Defender 2. Border of Insanity. Prohibition The Guard of Dungeon. Larva Mortus. Space Trader. Scrap Garden. Naval Warfare. Battle Ranch. War Legends. Sudden Strike Iwo Jima. Hot Zomb: Zombie Survival. You can ignore this particular bullet if you want, but if you're looking for a solution, a quick benchmark on another distro is usually worth a try.
Improve this answer. It would be persistent over reboots though. And if you want to avoid rebooting, you can combine the two — dyasny. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
0コメント