From: Shantanu Goel <sgoel01@yahoo.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 multiple thread streaming write performance with 2.6.9
Date: Thu, 28 Oct 2004 11:44:06 -0700 (PDT) [thread overview]
Message-ID: <20041028184406.55475.qmail@web12822.mail.yahoo.com> (raw)
In-Reply-To: <1098950444.2642.6.camel@laptop.fenrus.org>
Thanks for the pointer Arjan. That worked out well.
Here are the numbers I got for 2.6.9 with reservation
patches applied from 2.6.9-mm1.
ext3:data=ordered,reservation: 1: 47 48 48 (47)
ext3:data=ordered,reservation: 2: 47 44 45 (46)
ext3:data=ordered,reservation: 4: 45 43 45 (44)
ext3:data=writeback,reservation: 1: 47 49 48 (48)
ext3:data=writeback,reservation: 2: 48 46 44 (46)
ext3:data=writeback,reservation: 4: 46 45 45 (45)
ext2: 1: 53 55 54 (54)
ext2: 2: 42 52 51 (48)
ext2: 4: 21 26 25 (24)
xfs: 1: 53 53 53 (53)
xfs: 2: 48 53 51 (51)
xfs: 4: 43 47 46 (45)
--- Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 2004-10-27 at 21:04 -0700, Shantanu Goel
> wrote:
> > Hi,
> >
> > I am seeing extremely variable and poor
> performance
> > with ext3 in the presence of multiple streaming
> > writers. Below are the results of some tests I
> have
> > conducted with iozone. XFS appears to be most
> > consistent performer for this workload, followed
> by
> > ext2 and finally ext3. Has this been observed
> > elsewhere? If so, is it possible to tune ext3 to
> > perform better on this workload?
>
> yes you should use the reservations patch from the
> -mm tree;
> see http://people.redhat.com/arjanv/reservations.png
> for a graph of the difference
>
>
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
prev parent reply other threads:[~2004-10-28 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 4:04 Shantanu Goel
2004-10-28 8:00 ` Arjan van de Ven
2004-10-28 18:44 ` Shantanu Goel [this message]
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=20041028184406.55475.qmail@web12822.mail.yahoo.com \
--to=sgoel01@yahoo.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®