From: John Bradford <john@grabjohn.com>
To: rml@tech9.net (Robert Love)
Cc: sneakums@zork.net, linux-kernel@vger.kernel.org
Subject: Re: Performance of ext3 on large systems
Date: Mon, 17 Feb 2003 16:22:22 +0000 (GMT) [thread overview]
Message-ID: <200302171622.h1HGMMA8010529@darkstar.example.net> (raw)
In-Reply-To: <1045497374.12615.1.camel@phantasy> from "Robert Love" at Feb 17, 2003 10:56:14 AM
> > Actually, it makes sense in a way - noatime only speeds up reads, not
> > writes, (access time is always updated on a write), whereas a
> > journaled filesystem is presumably intended to be tuned for write
> > performance. So, for it's intended usage, not implementing noatime
> > shouldn't be a huge problem, although it would be useful.
>
> But updating the access time _is_ a write, even if its due to a read.
> And using 'noatime' does help, and it is implemented. I guess Andrew's
> statement was just misinterpreted, because this is what he said.
Well, yes, but that's not what I was saying - what was saying is that
if you are primarily reading anyway, there isn't much to be gained
from using EXT-3, over EXT-2.
If you are primarily writing, EXT-3 atime should be faster than EXT-2
noatime. EXT-3 notime will obviously be even faster.
John.
next prev parent reply other threads:[~2003-02-17 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 0:44 Martin J. Bligh
2003-02-17 1:18 ` Dave Hansen
2003-02-17 1:29 ` Andrew Morton
2003-02-17 15:20 ` Sean Neakums
2003-02-17 15:29 ` John Bradford
2003-02-17 15:56 ` Robert Love
2003-02-17 16:06 ` Sean Neakums
2003-02-17 16:22 ` John Bradford [this message]
2003-02-17 16:47 ` Matti Aarnio
2003-02-17 17:05 ` John Bradford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200302171622.h1HGMMA8010529@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=sneakums@zork.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®