public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: "Mr. Berkley Shands" <bshands@exegy.com>,
	Eric Sandeen <sandeen@sandeen.net>, Dave Lloyd <dlloyd@exegy.com>,
	linux-xfs@oss.sgi.com
Subject: Re: XFS and 2.6.18 -> 2.6.20-rc3
Date: Tue, 9 Jan 2007 18:25:35 +1100	[thread overview]
Message-ID: <20070109072535.GH44411608@melbourne.sgi.com> (raw)
In-Reply-To: <20070109012212.GG44411608@melbourne.sgi.com>

On Tue, Jan 09, 2007 at 12:22:12PM +1100, David Chinner wrote:
> On Mon, Jan 08, 2007 at 11:13:43AM -0600, Mr. Berkley Shands wrote:
> > My testbench is a 4 core Opteron (dual 275's) into
> > two LSI8408E SAS controllers, into 16 Seagate 7200.10 320GB satas.
> > Redhat ES4.4 (Centos 4.4). A slightly newer parted is needed
> > than the contemporary of Moses that is shipped with the O/S.
> > 
> > I have a standard burn in script that takes the 4 4-drive raid0's
> > and puts a GPT label on them, aligns the partitions to stripe
> > boundary's. It then proceeds to write 8GB files concurrently
> > onto all 4 raid drives.

I just ran up a similar test - single large file per device on a 4
core Xeon (woodcrest) with 16GB RAM, a single PCI-X SAS HBA and
12x10krpm 300GB SAS disks split into 3x4 disk dm raid zero stripes
on 2.6.18 and 2.6.20-rc3.

I see the same thing - 2.6.20-rc3 is more erractic and quite a
bit slower than 2.6.18 when going through XFS.

I suggest trying this on 2.6.20-rc3:

# echo 10 > /proc/sys/vm/dirty_ratio

That restored most of the lost performance and consistency
in my testing....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-01-09  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 17:13 XFS and 2.6.18 -> 2.6.20-rc3 Mr. Berkley Shands
2007-01-08 17:17 ` Eric Sandeen
2007-01-09  1:22 ` David Chinner
2007-01-09  7:25   ` David Chinner [this message]
2007-01-10 13:29     ` Mr. Berkley Shands
2007-01-10 22:08       ` David Chinner

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=20070109072535.GH44411608@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=bshands@exegy.com \
    --cc=dlloyd@exegy.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sandeen@sandeen.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