From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Daniel Zetterman <daniel.zetterman@gmail.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Faster read performance DURING (?) resync on raid10
Date: Sun, 28 Sep 2008 19:35:12 +0200 [thread overview]
Message-ID: <20080928173512.GA28823@rap.rap.dk> (raw)
In-Reply-To: <104f2a240809280406q22ab748s3dca796e70e63ec3@mail.gmail.com>
On Sun, Sep 28, 2008 at 01:06:09PM +0200, Daniel Zetterman wrote:
> Sorry guys, the offset is if course as stated near=2, far=1
>
> Isn't near=2, far=2 better for raid10?
>
a number of people say that near=1, far=2 is better.
you could try it out and see if there is any difference.
best regards
keld
>
> On Sun, Sep 28, 2008 at 12:45 PM, Daniel Zetterman
> <daniel.zetterman@gmail.com> wrote:
> > I'm using near=2, far=1, superblock version=00.90.03
> >
> > I'm not sure about offset, but its the default.
> >
> > I wan't to clearify one thing about the data, its not only a problem
> > with encryption over raid, you get the same drop without encryption...
> > but you can remedy it by setting up the readahead, which gives no
> > effect when using encryption.
> >
> >
> > On Sun, Sep 28, 2008 at 4:23 AM, Keld Jørn Simonsen <keld@dkuug.dk> wrote:
> >> On Sat, Sep 27, 2008 at 01:19:50AM +0200, Daniel Zetterman wrote:
> >>> I've done some more tests and here are the results:
> >>>
> >>> # bonnie++ during resync with readahead set to 512 (encrypted raid10)
> >>> kpax,4G,,,77308,21,34585,17,,,82073,33,384.8,1,,,,,,,,,,,,,
> >>
> >> It would be nice to know which layout (near,far,offset)
> >> that you are using for the test. The expected results are quite
> >> dependent on this.
> >>
> >> 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
--
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:[~2008-09-28 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 9:27 Faster read performance DURING (?) resync on raid10 sminded
2008-09-25 18:40 ` Keld J�rn Simonsen
2008-09-26 4:18 ` Neil Brown
2008-09-26 23:19 ` Daniel Zetterman
2008-09-28 2:23 ` Keld J�rn Simonsen
2008-09-28 10:45 ` Daniel Zetterman
2008-09-28 11:06 ` Daniel Zetterman
2008-09-28 17:35 ` Keld Jørn Simonsen [this message]
2008-09-26 8:03 ` John Robinson
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=20080928173512.GA28823@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=daniel.zetterman@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).