From: "Jon Nelson" <jnelson-linux-raid@jamponi.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: AWFUL reshape speed with raid5.
Date: Mon, 28 Jul 2008 13:55:28 -0500 [thread overview]
Message-ID: <cccedfc60807281155u7a6561a7jce3ca46799f46e4@mail.gmail.com> (raw)
In-Reply-To: <cccedfc60807281124w6301915bo88b8be45599f4fb3@mail.gmail.com>
Some more data points, observations, and questions.
For each test, I'd --create the array, drop the caches, --grow, and
then watch vmstat and also record the time between
kernel: md: resuming resync of md99 from checkpoint.
and
kernel: md: md99: resync done.
I found two things:
1. metadata version matters. Why?
2. VERY LITTLE I/O takes place (between 0 and 100KB/s, typically no
I/O at all) according to vmstat. Why? If it takes 1m34s to "grow" the
array, but no I/O is taking place, then what is actually taking so
long?
3. I removed the bitmap for these tests. Having a bitmap meant that
the overall speed was REALLY HORRIBLE.
The results:
metadata: time taken
0.9: 27s
1.0: 27s
1.1: 37s
1.2: 1m34s
Questions (repeated):
1. Why does the metadata version matter so much?
2. If no I/O is taking place, why does it take so long? [ NOTE: I/O
must be taking place but why doesn't vmstat show it? ]
--
Jon
next prev parent reply other threads:[~2008-07-28 18:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 17:39 AWFUL reshape speed with raid5 Jon Nelson
2008-07-28 18:14 ` Justin Piszcz
2008-07-28 18:24 ` Jon Nelson
2008-07-28 18:55 ` Jon Nelson [this message]
2008-07-28 19:17 ` Roger Heflin
2008-07-28 19:43 ` Justin Piszcz
2008-07-28 19:59 ` David Lethe
2008-07-28 20:56 ` Jon Nelson
2008-07-30 16:23 ` Bill Davidsen
2008-07-30 16:31 ` Jon Nelson
2008-07-30 17:08 ` Justin Piszcz
2008-07-30 17:48 ` Jon Nelson
2008-08-01 1:43 ` Neil Brown
2008-08-01 13:23 ` Jon Nelson
2008-08-01 15:57 ` Jon Nelson
2008-07-30 16:50 ` David Greaves
2008-07-30 17:24 ` Bill Davidsen
2008-08-01 1:26 ` Neil Brown
2008-08-01 13:14 ` Jon Nelson
2008-08-21 2:58 ` 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=cccedfc60807281155u7a6561a7jce3ca46799f46e4@mail.gmail.com \
--to=jnelson-linux-raid@jamponi.net \
--cc=jpiszcz@lucidpixels.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).