public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Langhorst <brad@langhorst.com>
To: Iustin Pop <iusty@k1024.org>
Cc: xfs@oss.sgi.com
Subject: Re: raid 10 su, sw settings
Date: Mon, 31 Dec 2007 15:55:01 -0500	[thread overview]
Message-ID: <1199134501.3437.21.camel@up> (raw)
In-Reply-To: <20071231201712.GA3679@teal.hq.k1024.org>


On Mon, 2007-12-31 at 21:17 +0100, Iustin Pop wrote:
> On Mon, Dec 31, 2007 at 02:07:27PM -0500, Justin Piszcz wrote:
> > On Mon, 31 Dec 2007, Brad Langhorst wrote:
> >> On Mon, 2007-12-31 at 12:04 -0500, Justin Piszcz wrote:
> >>
> >>>>
> >>>> Typical blocks/sec from iostat during large file movements is about
> >>>> 100M/s read and 80M/s write.
> >>>>
> >>>
> >>> #1 What type of performance do you expect with a 4-disk raid10?
> >>
> >> Are you saying that i should not expect more?
> >> I expect about 70% better performance, since I think a single disk
> >> should be able to do 100M/s. Maybe this is unreasonable?
> > A single disk may do 90MiB/s burst but not sustained for read or write, at 
> > least not cheap SATA disks and when you get toward the middle part of the 
> > disk the speed wil drop off significantly.  100MiB/s read and 80MiB/s write 
> > for RAID10 sounds about right to me.  Maybe someone else on the list with a 
> > similar configuration can chime in with their benchmarks.
> 
> I agree about the disk speed - 100MiB/s for SATA drives is a little bit
> too much to expect. And certainly, *only* in purely single-reader or
> single-writer sequential workloads.
> 
> I have the same config - 4 drive hw raid10 on 9650. A recent zcav log
> shows read speeds start at around 140MiB/s and decrease toward 75MiB/s.
> Since this is zcav from the bonie++ package, it doesn't take into
> account any filesystem or partitioning overhead.

I guess I should re-adjust my expectations

Any opinions on the partition layout? Did you go to special effort to
layout your partitions on the stripe boundaries (actually i don't really
understand this fully yet).

  reply	other threads:[~2007-12-31 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31  0:00 raid 10 su, sw settings Brad Langhorst
2007-12-31 17:04 ` Justin Piszcz
2007-12-31 18:43   ` Brad Langhorst
2007-12-31 19:07     ` Justin Piszcz
2007-12-31 20:17       ` Iustin Pop
2007-12-31 20:55         ` Brad Langhorst [this message]
2007-12-31 21:42           ` Iustin Pop
2007-12-31 22:54             ` Brad Langhorst
2008-01-01  0:15               ` Iustin Pop

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=1199134501.3437.21.camel@up \
    --to=brad@langhorst.com \
    --cc=iusty@k1024.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