From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Faster read performance DURING (?) resync on raid10
Date: Fri, 26 Sep 2008 09:03:44 +0100 [thread overview]
Message-ID: <48DC9760.90905@anonymous.org.uk> (raw)
In-Reply-To: <19666016.post@talk.nabble.com>
On 25/09/2008 10:27, sminded wrote:
> The strange thing is that I can see a significant increase in read
> performance (about 20%) when running the tests DURING the raid resync phase
> directly after the raid creation
Is it possible this is because the resync process has already read part
of the disc into cache when your test starts, effectively poisioning the
test results?
Cheers,
John.
prev parent reply other threads:[~2008-09-26 8:03 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
2008-09-26 8:03 ` John Robinson [this message]
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=48DC9760.90905@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--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).