From: Eric Sandeen <sandeen@redhat.com>
To: sftf <sftf-misc@mail.ru>
Cc: valerie.clement@bull.net, linux-ext4@vger.kernel.org
Subject: Re: Performance testing results
Date: Wed, 27 Jun 2007 23:52:24 -0400 [thread overview]
Message-ID: <46833078.3070609@redhat.com> (raw)
In-Reply-To: <1692756695.20070628104652@mail.ru>
sftf wrote:
> Hi!
> IMHO this test is not 100% correct.
> ext3 | data=writeback
> ext4 | data=writeback,extents,delalloc
> xfs | defaults is ordered !
>
> So you have compared ext's in writeback (which fastest mode) vs xfs in ordered.
Actually xfs's default (only) mode is more like writeback than ordered.
So that's a fair comparison. I bet it is xfs's barriers that hurt
it, though - while they are pretty much required on a single disk with a
volatile write cache, I think xfs's barrier implementation hurts it more
than barriers for ext*
-Eric
next prev parent reply other threads:[~2007-06-28 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 4:46 Performance testing results sftf
2007-06-28 3:52 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-27 16:15 Valerie Clement
2007-06-27 21:19 ` Mingming Cao
2007-06-28 13:47 ` Jean noel Cordenner
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=46833078.3070609@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sftf-misc@mail.ru \
--cc=valerie.clement@bull.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;
as well as URLs for NNTP newsgroup(s).