From: NeilBrown <neilb@suse.de>
To: Manish Awasthi <manish.awasthi@caviumnetworks.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: md raid performance with 3-18-rc3
Date: Wed, 3 Dec 2014 17:21:01 +1100 [thread overview]
Message-ID: <20141203172101.17859aee@notabene.brown> (raw)
In-Reply-To: <54758B3B.5080907@caviumnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]
On Wed, 26 Nov 2014 13:41:39 +0530 Manish Awasthi
<manish.awasthi@caviumnetworks.com> wrote:
> Whatever data I have on comparison is attached, I have consolidated this
> from log files to excel. See if this helps.
raid_3_18_performance.xls shows read throughput to be consistently 20% down
on 3.18 compared to 3.6.11.
Writes are a few percent better for 4G/8G files, 20% better for 16G/32G files.
unchanged above that.
Given that you have 8G of RAM, that seems like it could be some change in
caching behaviour, and not necessarily a change in RAID behaviour.
The CPU utilization roughly follows the throughput: 40% higher when write
throughput is 20% better.
Could you check if the value of /proc/sys/vm/dirty_ratio is the same for both
tests. That number has changed occasionally and could affect these tests.
The second file, 3SSDs-perf-2-Cores-3.18-rc1 has the "change" numbers
negative where I expected positive.. i.e. negative mean an increase.
Writes consistently have higher CPU utilisation.
Reads consistently have much lower CPU utilization.
I don't know what that means ... it might not mean anything.
Could you please run the tests between the two kernels *with* RAID. i.e.
directly on an SSD. That will give us a baseline for what changes are caused
by other parts of the kernel (filesystem, block layer, MM, etc). Then we can
see how much change RAID5 is contributing.
The third file, 3SSDs-perf-4Core.xls seems to show significantly reduced
throughput across the board.
CPU utilization is less (better) for writes, but worse for reads. That is
the reverse of what the second file shows.
I might try running some tests across a set of kernel versions and see what I
can come up with.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-12-03 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 8:10 md raid performance with 3-18-rc3 Manish Awasthi
2014-11-25 2:37 ` NeilBrown
[not found] ` <54758B3B.5080907@caviumnetworks.com>
2014-12-03 5:19 ` NeilBrown
2014-12-03 6:21 ` NeilBrown [this message]
[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=20141203172101.17859aee@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=manish.awasthi@caviumnetworks.com \
/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).