public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 16:29:31 -0800	[thread overview]
Message-ID: <3CA263EB.2576ED4A@zip.com.au> (raw)
In-Reply-To: <3CA20698.E8A9826E@zip.com.au> <Pine.LNX.4.33.0203272354430.17217-100000@sphinx.mythic-beasts.com>

Matthew Kirkwood wrote:
> 
> On Wed, 27 Mar 2002, Andrew Morton 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.
> 
> Here we are.  This is with just a 200Mb journal (the partition
> is only a little over 1Gb, and the datafiles grow fairly big,
> so I didn't brave making it any bigger).
> 
>         tuning? single  ir      mx-ir   oltp    mixed-oltp
>                 (sec)   (tps)   (sec)   (tps)   (sec)
> ext3    bn      1285.32 65.98   1996.41 90.05   307.79
> ext3-wb bn      1287.31 98.42   2149.38 125.13  236.02
> ext3-jd bn      1306.90 72.07   1813.54 125.15  305.27

Oh well.

It sounds like a useful and valid workload to optimise
for.  So I'll take you up on the offer of those scripts,
please.

-

  reply	other threads:[~2002-03-28  0:31 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 [this message]
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=3CA263EB.2576ED4A@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