All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Langhorst <brad@langhorst.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: raid 10 su, sw settings
Date: Mon, 31 Dec 2007 13:43:06 -0500	[thread overview]
Message-ID: <1199126586.3437.10.camel@up> (raw)
In-Reply-To: <Pine.LNX.4.64.0712311203220.23402@p34.internal.lan>


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?


> #2 You should be able to umount/mount with the new sizes, although I have 
> not tested it myself b/c I typically use sw raid here (sunit/etc is 
> optimized for sw raid).
I am able to do the remount, but it seems to have had no impact. 
I don't know why but I see 3 possibilities:
 - Perhaps because su/sw settings  don't matter very much.
 - maybe it didn't take effect (rebooting this system is not a preferred
option)
 - maybe it doesn't matter if the partition layout is not optimized.

Brad

  reply	other threads:[~2007-12-31 18:43 UTC|newest]

Thread overview: 10+ 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 [this message]
2007-12-31 19:07     ` Justin Piszcz
2007-12-31 20:17       ` Iustin Pop
2007-12-31 20:55         ` Brad Langhorst
2007-12-31 21:42           ` Iustin Pop
2007-12-31 22:54             ` Brad Langhorst
2008-01-01  0:15               ` Iustin Pop
2007-12-31 18:53 ` pg_mh, Peter Grandi

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=1199126586.3437.10.camel@up \
    --to=brad@langhorst.com \
    --cc=jpiszcz@lucidpixels.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.