From: Bernd Schubert <bs@q-leap.de>
To: David Chinner <dgc@sgi.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Jon Collette <jon@etelos.com>,
Joshua Baker-LePain <jlb17@duke.edu>,
linux-ide-arrays@lists.math.uh.edu, linux-raid@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: 3ware 9650 tips
Date: Mon, 16 Jul 2007 14:39:22 +0200 [thread overview]
Message-ID: <200707161439.23159.bs@q-leap.de> (raw)
In-Reply-To: <20070716122225.GB31489@sgi.com>
On Monday 16 July 2007 14:22:25 David Chinner wrote:
> You can see from the ext3 graph that it comes to a screeching halt
> every 5s (probably when pdflush runs) and at all other times the
> seek rate is >10,000 seeks/s. That's pretty bad for a brand new,
> empty filesystem and the only way it is sustained is the fact that
> the disks have their write caches turned on. ext4 will probably show
> better results, but I haven't got any of the tools installed to be
> able to test it....
I recently did some filesystem throuput tests, you may find it here
http://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/lustre/performance/
ldiskfs is ext3+extents+mballoc+some-smaller-patches, so is almost ext4
(delayed allocation is still missing, but the clusterfs/lustre people didn't
port it and I'm afraid of hard to detect filesystem corruptions if I include
it myself).
Write performance is still slower than with xfs and I'm really considering to
try to use xfs in lustre.
Cheers,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
next prev parent reply other threads:[~2007-07-16 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.0.999.0707131356520.25773@chaos.egr.duke.edu>
[not found] ` <Pine.LNX.4.64.0707131434470.31742@p34.internal.lan>
[not found] ` <4697CA4D.6020304@etelos.com>
2007-07-13 19:36 ` 3ware 9650 tips Justin Piszcz
2007-07-16 2:41 ` David Chinner
2007-07-16 12:22 ` David Chinner
2007-07-16 12:39 ` Bernd Schubert [this message]
2007-07-16 15:50 ` Eric Sandeen
2007-07-16 22:21 ` David Chinner
2007-07-16 15:43 ` Joshua Baker-LePain
2007-07-16 17:15 ` [Advocacy] " Bryan J. Smith
[not found] ` <200707162040.00062.a1426z@gawab.com>
2007-07-16 17:48 ` Matthew Wilcox
2007-07-16 18:28 ` [RFC] VFS: data=ordered (was: [Advocacy] Re: 3ware 9650 tips) Al Boldi
2007-07-16 19:02 ` Matthew Wilcox
2007-07-16 18:38 ` [Advocacy] Re: 3ware 9650 tips Bryan J. Smith
2007-07-16 17:34 ` Stuart Levy
2007-07-16 18:44 ` [Advocacy] " Bryan J. Smith
2007-07-17 17:30 ` Simon Matter
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=200707161439.23159.bs@q-leap.de \
--to=bs@q-leap.de \
--cc=dgc@sgi.com \
--cc=jlb17@duke.edu \
--cc=jon@etelos.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide-arrays@lists.math.uh.edu \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.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