From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: adfas asd <chimera_god@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Remote NAS
Date: Wed, 23 Sep 2009 23:01:45 +0200 [thread overview]
Message-ID: <20090923210145.GA23285@rap.rap.dk> (raw)
In-Reply-To: <501250.73276.qm@web38802.mail.mud.yahoo.com>
On Wed, Sep 23, 2009 at 07:59:09AM -0700, adfas asd wrote:
> --- On Wed, 9/23/09, Keld Jørn Simonsen <keld@dkuug.dk> wrote:
> > There is a setup described at
> >
> > http://linux-raid.osdl.org/index.php/Preventing_against_a_failing_disk
> >
> > You can substitute raid10,o2 for raid10,f2 for the root
> > partitions etc.
> >
> > Anyway, raid10,f2 should be faster than raid10,o2, for at
> > least reads,
> > while for writes it is about the same performance given
> > that you employ
> > a file system.
>
> Thanks keld. I used this procedure, which does about the same thing and seems more clear, adapting it to RAID10-o2:
> http://www.howtoforge.com/software-raid1-grub-boot-debian-etch
>
> I could find no performance comparison with far and offset, and knew that far improved on reads, so since offset came later inferred that it would have improved writes. No objective data to confirm otherwise.
There are a number of performance tests at:
http://linux-raid.osdl.org/index.php/Performance
Writes are about the same for RAID10 types and RAID1.
This is also what theory would tell for random writes, given that they
are random, and that the elevator algorithm of the file system optimizes
the writing.
Yes, offset came after far, but Neil Brown said that offset was
implemented to make Linux MD align to RAID standards. It was not
necessarily meant to be better than far.
I think it is hard to beat raid10 far on reads (but then I am also the
one that invented the layout). As said for random reading and writing
the theory says that all mirrored raid types perform equally, and tests
verify this. Maybe far layout even has an edge for random reading, in
theory it should, but I have not seen tests really verifying that.
best regards
Keld
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-23 21:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 19:38 Remote NAS adfas asd
2009-09-22 20:09 ` Robin Hill
2009-09-22 21:56 ` adfas asd
2009-09-23 7:57 ` Robin Hill
2009-09-23 9:13 ` Keld Jørn Simonsen
2009-09-23 14:59 ` adfas asd
2009-09-23 21:01 ` Keld Jørn Simonsen [this message]
2009-09-23 22:58 ` adfas asd
2009-09-23 14:52 ` adfas asd
2009-09-23 15:29 ` Robin Hill
2009-09-23 15:44 ` adfas asd
2009-09-23 16:10 ` Robin Hill
2009-09-27 20:19 ` Leslie Rhorer
2009-09-28 14:07 ` adfas asd
2009-09-28 14:15 ` Thomas Fjellstrom
2009-09-29 14:40 ` adfas asd
2009-09-29 9:25 ` Leslie Rhorer
2009-09-27 20:44 ` Leslie Rhorer
2009-09-27 22:00 ` Leslie Rhorer
2009-09-29 14:15 ` adfas asd
2009-09-30 15:36 ` Leslie Rhorer
[not found] <228497.14504.qm@web38801.mail.mud.yahoo.com>
2009-09-29 10:09 ` Leslie Rhorer
[not found] <20090923200257.GA19027@cthulhu.home.robinhill.me.uk>
2009-09-23 23:08 ` adfas asd
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 16:21 adfas asd
2009-09-27 19:39 ` Leslie Rhorer
2009-09-27 20:09 ` Leslie Rhorer
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=20090923210145.GA23285@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=chimera_god@yahoo.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).