From: keld@keldix.com
To: Jessie Evangelista <jessie.evangelista@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>, Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: raid10n2/xfs setup guidance on write-cache/barrier
Date: Thu, 15 Mar 2012 18:15:49 +0100 [thread overview]
Message-ID: <20120315171548.GA30531@www5.open-std.org> (raw)
In-Reply-To: <CAA8mOyDquGX0kEbQSpo=S0EYdNvXNBQ6ZLnb5Sc7uvCPYB+xqA@mail.gmail.com>
On Fri, Mar 16, 2012 at 12:52:19AM +0800, Jessie Evangelista wrote:
> Hi keld,
>
> On Thu, Mar 15, 2012 at 11:25 PM, <keld@keldix.com> wrote:
> > On Thu, Mar 15, 2012 at 02:07:25PM +0000, Peter Grandi wrote:
> >> >>> I want to create a raid10,n2 using 3 1TB SATA drives.
> >> >>> I want to create an xfs filesystem on top of it. The
> >> >>> filesystem will be used as NFS/Samba storage.
> >>
> >> Consider also an 'o2' layout (it is probably the same thing for a
> >> 3 drive RAID10) or even a RAID5, as 3 drives and this usage seems
> >> one of the few cases where RAID5 may be plausible.
> >
> > Well, for a file server like NFS/Samba, you could also consider raid10,f2.
> > I would think you could get about double the read performance compared to n2 and o2
> > layouts, and also for individual read transfers on a running system
> > you would get somthing like double the read performance.
> > Write performance could be somewhat slower (0 to 10 %) bot as users
> > are not waiting for writes to complete, they will probably not notice.
>
> I also plan to try raid10f2. Did you do your own benchmarks or are you
> quoting someone elses?
Both, look at our wiki: https://raid.wiki.kernel.org/articles/p/e/r/Performance.html
Best regards
keld
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-15 17:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA8mOyDKrWg0QUEHxcD4ocXXD42nJu0TG+sXjC4j2RsigHTcmw@mail.gmail.com>
[not found] ` <4F61803A.60009@hardwarefreak.com>
[not found] ` <CAA8mOyCzs36YD_QUMq25HQf8zuq1=tmSTPjYdoFJwy2Oq9sLmw@mail.gmail.com>
2012-03-15 14:07 ` raid10n2/xfs setup guidance on write-cache/barrier Peter Grandi
2012-03-15 15:25 ` keld
2012-03-15 16:52 ` Jessie Evangelista
2012-03-15 17:15 ` keld [this message]
2012-03-15 17:40 ` keld
2012-03-15 16:18 ` Jessie Evangelista
2012-03-15 23:00 ` Peter Grandi
2012-03-16 3:36 ` Jessie Evangelista
2012-03-16 11:06 ` Michael Monnerie
2012-03-16 12:21 ` Peter Grandi
2012-03-16 17:15 ` Brian Candler
2012-03-17 15:35 ` Peter Grandi
2012-03-17 21:39 ` raid10n2/xfs setup guidance on write-cache/barrier (GiB alignment) Zdenek Kaspar
2012-03-18 0:08 ` Peter Grandi
2012-03-26 19:50 ` raid10n2/xfs setup guidance on write-cache/barrier Martin Steigerwald
2012-03-17 4:21 ` NOW:Peter goading Dave over delaylog - WAS: " Stan Hoeppner
2012-03-17 22:34 ` Dave Chinner
2012-03-18 2:09 ` Peter Grandi
2012-03-18 11:25 ` Peter Grandi
2012-03-18 14:00 ` Christoph Hellwig
2012-03-18 19:17 ` Peter Grandi
2012-03-19 9:07 ` Stan Hoeppner
2012-03-20 12:34 ` Jessie Evangelista
2012-03-18 18:08 ` Stan Hoeppner
2012-03-22 21:26 ` Peter Grandi
2012-03-23 5:10 ` Stan Hoeppner
2012-03-23 22:48 ` Martin Steigerwald
2012-03-24 1:27 ` Peter Grandi
2012-03-24 16:27 ` GNU 'tar', Schilling's 'tar', write-cache/barrier Peter Grandi
2012-03-24 17:11 ` Brian Candler
2012-03-24 18:35 ` Peter Grandi
[not found] ` <4F633121.10800@hardwarefreak.com>
[not found] ` <CAKuK5J3GHgWcnYLqwRV8s_wMjO2nBVf7h=yONtn90kPn9A_3Gg@mail.gmail.com>
[not found] ` <CAKuK5J11JTdwZSBWj7DH7c+hE--MVNQVVrcKXaV2AO-wEpWBog@mail.gmail.com>
2012-03-16 19:28 ` raid10n2/xfs setup guidance on write-cache/barrier Peter Grandi
2012-03-17 0:02 ` Stan Hoeppner
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=20120315171548.GA30531@www5.open-std.org \
--to=keld@keldix.com \
--cc=jessie.evangelista@gmail.com \
--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