From: Arjan van de Ven <arjan@infradead.org>
To: Shantanu Goel <sgoel01@yahoo.com>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 multiple thread streaming write performance with 2.6.9
Date: Thu, 28 Oct 2004 10:00:45 +0200 [thread overview]
Message-ID: <1098950444.2642.6.camel@laptop.fenrus.org> (raw)
In-Reply-To: <20041028040421.80505.qmail@web12826.mail.yahoo.com>
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
next prev parent reply other threads:[~2004-10-28 8:01 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 [this message]
2004-10-28 18:44 ` Shantanu Goel
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=1098950444.2642.6.camel@laptop.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgoel01@yahoo.com \
/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®