From: David Chinner <dgc@sgi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Peter Rabbitson <rabbit@rabbit.us>,
linux-raid@vger.kernel.org, xfs@oss.sgi.com,
Alan Piszcz <ap@solarrain.com>
Subject: Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
Date: Fri, 29 Jun 2007 08:05:37 +1000 [thread overview]
Message-ID: <20070628220537.GC31489@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706280426500.1406@p34.internal.lan>
On Thu, Jun 28, 2007 at 04:27:15AM -0400, Justin Piszcz wrote:
>
>
> On Thu, 28 Jun 2007, Peter Rabbitson wrote:
>
> >Justin Piszcz wrote:
> >>mdadm --create \
> >> --verbose /dev/md3 \
> >> --level=5 \
> >> --raid-devices=10 \
> >> --chunk=1024 \
> >> --force \
> >> --run
> >> /dev/sd[cdefghijkl]1
> >>
> >>Justin.
> >
> >Interesting, I came up with the same results (1M chunk being superior)
> >with a completely different raid set with XFS on top:
> >
> >mdadm --create \
> > --level=10 \
> > --chunk=1024 \
> > --raid-devices=4 \
> > --layout=f3 \
> > ...
> >
> >Could it be attributed to XFS itself?
More likely it's related to the I/O size being sent to the disks. The larger
the chunk size, the larger the I/o hitting each disk. I think the maximum I/O
size is 512k ATM on x86(_64), so a chunk of 1MB will guarantee that there are
maximally sized I/Os being sent to the disk....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-06-28 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 23:20 Fastest Chunk Size w/XFS For MD Software RAID = 1024k Justin Piszcz
2007-06-27 23:20 ` Justin Piszcz
2007-06-27 23:24 ` Justin Piszcz
2007-06-28 5:08 ` David Chinner
2007-06-28 7:53 ` David Greaves
2007-06-28 8:07 ` Justin Piszcz
[not found] ` <46832E60.9000006@rabbit.us>
2007-06-28 8:07 ` Justin Piszcz
[not found] ` <46837056.4050306@rabbit.us>
2007-06-28 8:27 ` Justin Piszcz
2007-06-28 22:05 ` David Chinner [this message]
2007-06-28 9:05 ` Matti Aarnio
2007-06-28 13:27 ` Jon Nelson
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=20070628220537.GC31489@sgi.com \
--to=dgc@sgi.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=rabbit@rabbit.us \
--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