From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-raid@vger.kernel.org
Subject: *terrible* direct-write performance with raid5
Date: Tue, 22 Feb 2005 20:39:41 +0300 [thread overview]
Message-ID: <421B6E5D.6030004@tls.msk.ru> (raw)
When debugging some other problem, I noticied that
direct-io (O_DIRECT) write speed on a software raid5
is terrible slow. Here's a small table just to show
the idea (not numbers by itself as they vary from system
to system but how they relate to each other). I measured
"plain" single-drive performance (sdX below), performance
of a raid5 array composed from 5 sdX drives, and ext3
filesystem (the file on the filesystem was pre-created
during tests). Speed measurements performed with 8Kbyte
buffer aka write(fd, buf, 8192*1024), units a Mb/sec.
write read
sdX 44.9 45.5
md 1.7* 31.3
fs on md 0.7* 26.3
fs on sdX 44.7 45.3
"Absolute winner" is a filesystem on top of a raid5 array:
700 kilobytes/sec, sorta like a 300-megabyte ide drive some
10 years ago...
The raid5 array built with mdadm with default options, aka
Layout = left-symmetric, Chunk Size = 64K. The same test
with raid0 or raid1 for example shows quite good performance
(still not perfect but *much* better than for raid5).
It's quite interesting how I/O speed is different for fs on md
vs fs on sdX case - with fs on sdX, filesystem code adds almost
nothing to the plain partition speed, while it makes alot of
difference when used on top of an md device.
Comments anyone? ;)
Thanks.
/mjt
next reply other threads:[~2005-02-22 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 17:39 Michael Tokarev [this message]
2005-02-22 20:11 ` *terrible* direct-write performance with raid5 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
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=421B6E5D.6030004@tls.msk.ru \
--to=mjt@tls.msk.ru \
--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).