User: Password:
|
|
Subscribe / Log in / New account

Re: [PATCH 00/23] per device dirty throttling -v8

From:  Ingo Molnar <mingo-AT-elte.hu>
To:  Alan Cox <alan-AT-lxorguk.ukuu.org.uk>
Subject:  Re: [PATCH 00/23] per device dirty throttling -v8
Date:  Sat, 4 Aug 2007 23:03:51 +0200
Message-ID:  <20070804210351.GA9784@elte.hu>
Cc:  J??rn Engel <joern-AT-logfs.org>, Jeff Garzik <jeff-AT-garzik.org>, Linus Torvalds <torvalds-AT-linux-foundation.org>, Peter Zijlstra <a.p.zijlstra-AT-chello.nl>, linux-mm-AT-kvack.org, Linux Kernel Mailing List <linux-kernel-AT-vger.kernel.org>, miklos-AT-szeredi.hu, akpm-AT-linux-foundation.org, neilb-AT-suse.de, dgc-AT-sgi.com, tomoki.sekiyama.qu-AT-hitachi.com, nikita-AT-clusterfs.com, trond.myklebust-AT-fys.uio.no, yingchao.zhou-AT-gmail.com, richard-AT-rsk.demon.co.uk, david-AT-lang.hm
Archive-link:  Article


* Ingo Molnar <mingo@elte.hu> wrote:

> noatime,nodiratime gave 50% of wall-clock kernel rpm build performance 
> improvement for Dave Jones, on a beefy box. Unless i misunderstood 
> what you meant under 'fraction of a percent' your numbers are _WAY_ 
> off. Atime updates are a _huge everyday deal_, from laptops to 
> servers. Everywhere on the planet. Give me a Linux desktop anywhere 
> and i can tell you whether it has atimes on or off, just by clicking 
> around and using apps (without looking at the mount options). That's 
> how i notice it that i forgot to turn off atime on any newly installed 
> system - the system has weird desktop lags and unnecessary disk 
> trashing.

i cannot over-emphasise how much of a deal it is in practice. Atime 
updates are by far the biggest IO performance deficiency that Linux has 
today. Getting rid of atime updates would give us more everyday Linux 
performance than all the pagecache speedups of the past 10 years, 
_combined_.

it's also perhaps the most stupid Unix design idea of all times. Unix is 
really nice and well done, but think about this a bit:

   ' For every file that is read from the disk, lets do a ... write to
     the disk! And, for every file that is already cached and which we
     read from the cache ... do a write to the disk! '

tell that concept to any rookie programmer who knows nothing about 
kernels and the answer will be: 'huh, what? That's gross!'. And Linux 
does this unconditionally for everything, and no, it's not only done on 
some high-security servers that need all sorts of auditing enabled that 
logs every file read - no, it's done by 99% of the Linux desktops and 
servers. For the sake of some lazy mailers that could now be using 
inotify, and for the sake of ... nothing much, really - forensics 
software perhaps.

	Ingo


(Log in to post comments)


Copyright © 2007, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds