public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Matthew Kirkwood <matthew@hairy.beasts.org>,
	Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Filesystem benchmarks: ext2 vs ext3 vs jfs vs minix
Date: Wed, 27 Mar 2002 18:17:31 -0800	[thread overview]
Message-ID: <20020328021731.GC8627@matchmail.com> (raw)
In-Reply-To: <p73y9ge3xww.fsf@oldwotan.suse.de> <Pine.LNX.4.33.0203271419230.28110-100000@sphinx.mythic-beasts.com> <20020327180247.GU21133@turbolinux.com>

On Wed, Mar 27, 2002 at 11:02:47AM -0700, Andreas Dilger wrote:
> On Mar 27, 2002  14:47 +0000, Matthew Kirkwood wrote:
> > Postgres doesn't pre-allocate datafiles.  They reckon it's not
> > their job to implement a filesystem, and I'm inclined to agree.
> > They do prefer fdatasync on datafiles and (I think) O_DATASYNC
> > for their journal files where available, but I haven't checked
> > that my build is doing that.
> 
> If the I/O is normally sync driven, you should consider testing ext3
> with "data=journal".  While this seems counterintuitive because it is
> writing the data to disk twice, it can often be faster in real-world
> "bursty" environments because the sync I/O goes to the journal in one
> contiguous write, and it can then be written to the rest of the fs
> asynchronously safely. 

Don't forget to have enough extra memory so that it can have time to do
those async writes later.

When is ext3 going to get high and low watermarks?

Currently it hits a (50%?) high usage level and then sync writes the entire
journal contents. :(  Has that changed?

  parent reply	other threads:[~2002-03-28  2:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0203271323330.24894-100000@sphinx.mythic-beasts.com.suse.lists.linux.kernel>
2002-03-27 14:09 ` Filesystem benchmarks: ext2 vs ext3 vs jfs vs minix Andi Kleen
2002-03-27 14:47   ` Matthew Kirkwood
2002-03-27 15:35     ` Michael Alan Dorman
2002-03-27 17:51     ` Andrew Morton
2002-03-28  0:04       ` Matthew Kirkwood
2002-03-28  0:29         ` Andrew Morton
2002-03-28  0:42           ` Matthew Kirkwood
2002-03-28 11:11         ` Matthew Kirkwood
2002-03-27 18:02     ` Andreas Dilger
2002-03-28  0:09       ` Matthew Kirkwood
2002-03-28  2:17       ` Mike Fedyk [this message]
2002-03-27 13:54 Matthew Kirkwood
2002-03-27 14:17 ` Florin Andrei

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=20020328021731.GC8627@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@hairy.beasts.org \
    /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