From: Andrew Morton <akpm@zip.com.au>
To: Matthew Kirkwood <matthew@hairy.beasts.org>
Cc: 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 09:51:20 -0800 [thread overview]
Message-ID: <3CA20698.E8A9826E@zip.com.au> (raw)
In-Reply-To: <p73y9ge3xww.fsf@oldwotan.suse.de> <Pine.LNX.4.33.0203271419230.28110-100000@sphinx.mythic-beasts.com>
Matthew Kirkwood wrote:
>
> ...
> Yeah, I thought it was a little odd. Postgres does so much
> fsync()ing that I thought it may just have been that the lower
> overhead won out over ext2's cleverer layout. All the I/O was
> basically fsync-driven, so this test was only about write
> performance.
>
For fsync-intensive loads ext3's best mode is generally
data=journal. That way, an fsync is satisfied by a nice
single linear write to the journal.
With a high volume of data you'll quickly exhaust the
journal space so it would also be beneficial to create
a monster journal with, say, mke2fs -J 400.
-
next prev parent reply other threads:[~2002-03-27 17:53 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 [this message]
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
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=3CA20698.E8A9826E@zip.com.au \
--to=akpm@zip.com.au \
--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