From: ptb@lab.it.uc3m.es (Peter T. Breuer)
To: linux-raid@vger.kernel.org
Subject: Re: *terrible* direct-write performance with raid5
Date: Wed, 23 Feb 2005 18:55:39 +0100 [thread overview]
Message-ID: <rlsue2-0sc.ln1@news.it.uc3m.es> (raw)
In-Reply-To: 421CBF7D.20801@tls.msk.ru
Michael Tokarev <mjt@tls.msk.ru> wrote:
> (note raid5 performs faster than a single drive, it's expectable
> as it is possible to write to several drives in parallel).
Each raid5 write must include at least ONE write to a target. I think
you're saying that the writes go to different targets from time to time
and that when the targets are the bottlenecks then you get faster than
normal response.
Hmmmm. That's actually quite difficult to calculate, because if say you
have three raid disks, then every time you write to the array you write
to two of those three (foget the read, which will come via readahead and
buffers). Suppose that's no slower than one write to one disk, how
could you get any speed INCREASE?
Well, only by writing to a different two out of the three each time, or
near each time. If you first write to AB, then to BC, then to CA, and
repeat, then you have written 3 times but only kept each disk busy 2/3
of the time, so I suppose there is some opportunity for pipelining. Can
anyone see where?
A B C A B C ...
B C A B C A ...
1 2 3 1 2 3
Maybe like this:
A1 A3 A1 A3 ...
B1 B2 B1 B2 ...
C2 C3 C2 C3 ...
Yes. That seems to preserve local order and go 50% faster.
Peter
prev parent reply other threads:[~2005-02-23 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 17:39 *terrible* direct-write performance with raid5 Michael Tokarev
2005-02-22 20:11 ` Peter T. Breuer
2005-02-22 21:43 ` Michael Tokarev
2005-02-22 22:27 ` Peter T. Breuer
2005-02-22 23:08 ` dean gaudet
2005-02-23 17:38 ` Michael Tokarev
2005-02-23 17:55 ` Peter T. Breuer [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=rlsue2-0sc.ln1@news.it.uc3m.es \
--to=ptb@lab.it.uc3m.es \
--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).