From: Manish Awasthi <manish.awasthi@caviumnetworks.com>
To: linux-raid@vger.kernel.org
Subject: md raid performance with 3-18-rc3
Date: Mon, 24 Nov 2014 13:40:06 +0530 [thread overview]
Message-ID: <5472E7DE.5070702@caviumnetworks.com> (raw)
Hi,
We benchmarked the md raid driver performance on 3-18-rc3 kernel and
compared the results with that of 3.6.11. The reason for this exercise
is to understand if multithreaded raid driver has any performance
benefits over 3.6.11 which is single threaded. Here are some details
about the setup
System: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz 4 cores (8threads),
8GB RAM.
Setup: 3 SSDs create a raid5 array
test tool: iozone (only read/re-read, write/re-write tested), blocksize:
4k-64k, filesize: 1Gig to 200Gig
Comparison was done for speed of data transfer in kBytes/sec and also
the CPU utilization as reported by iozone.
raid on 3.18.0-rc3 performed much worse than raid on 3.6.11.
Read/Write: raid on 3.18.0-rc3 operated at almost half the speed of raid
on 3.6.11
CPU Utilization: With md raid on 3.18.0-rc3, the CPU utilization was
less than half of md raid on 3.6.11 on WRITE operations. However, for
READ operations, 3.18-0.rc3 had more CPU utilization than 3.6.11.
Also, I noticed that scaling up the CPU cores of the system scales down
the raid througput with 3.18.0-rc3.
I do have detailed logs of the comparison but I'm not sure I should send
those on this mailing list.
If my observation aligns with someone else's, then what is really the
gain with multithreaded raid.
Manish
next reply other threads:[~2014-11-24 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 8:10 Manish Awasthi [this message]
2014-11-25 2:37 ` md raid performance with 3-18-rc3 NeilBrown
[not found] ` <54758B3B.5080907@caviumnetworks.com>
2014-12-03 5:19 ` NeilBrown
2014-12-03 6:21 ` NeilBrown
[not found] ` <5486B15C.8060109@caviumnetworks.com>
2014-12-09 8:24 ` Manish Awasthi
2014-12-09 8:26 ` Manish Awasthi
[not found] ` <5487FD79.7000002@caviumnetworks.com>
2015-01-06 9:49 ` Manish Awasthi
2015-01-07 10:52 ` Manish Awasthi
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=5472E7DE.5070702@caviumnetworks.com \
--to=manish.awasthi@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.