From: Roman Mamedov <rm@romanrm.net>
To: Jake Yao <jgyao1@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: performance of raid5 on fast devices
Date: Tue, 17 Jan 2017 10:10:43 +0500 [thread overview]
Message-ID: <20170117101043.78e80bdc@natsu> (raw)
In-Reply-To: <CA+Dh761_kVPEcRdFEAo72Wif_t-G7RpgyoKGetEFveyMpaYD1w@mail.gmail.com>
On Mon, 16 Jan 2017 21:35:21 -0500
Jake Yao <jgyao1@gmail.com> wrote:
> I have a raid5 array on 4 NVMe drives, and the performance on the
> array is only marginally better than a single drive. Unlike a similar
> raid5 array on 4 SAS SSD or HDD, the performance on array is 3x
> better than a single drive, which is expected.
>
> It looks like when the single kernel thread associated with the raid
> device running at 100%, the array performance hit its peak. This can
> happen easily for fast devices like NVMe.
>
> This can reproduced by creating a raid5 with 4 ramdisks as well, and
> comparing performance on the array and one ramdisk. Sometimes the
> performance on the array is worse than a single ramdisk.
>
> The kernel version is 4.9.0-rc3 and mdadm is release 3.4, no write
> journal is configured.
>
> Is this a known issue?
How do you measure the performance?
Sure it may be CPU-bound in the end, but also why not try the usual
optimization tricks, such as:
* increase your stripe_cache_size, it's not uncommon that this can speed up
linear writes by as much as several times;
* if you meant reads, you could look into read-ahead settings for the array;
* and in both cases, try experimenting with different stripe sizes (if you
were using 512K, try with 64K stripes).
--
With respect,
Roman
next prev parent reply other threads:[~2017-01-17 5:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 2:35 performance of raid5 on fast devices Jake Yao
2017-01-17 3:10 ` Stan Hoeppner
2017-01-17 5:04 ` Coly Li
2017-01-17 15:22 ` Jake Yao
2017-01-17 5:10 ` Roman Mamedov [this message]
2017-01-17 15:28 ` Jake Yao
2017-01-17 21:04 ` Heinz Mauelshagen
2017-01-18 19:25 ` Jake Yao
2017-01-20 14:58 ` Coly Li
2017-01-23 22:20 ` Jake Yao
2017-01-24 7:11 ` Coly Li
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=20170117101043.78e80bdc@natsu \
--to=rm@romanrm.net \
--cc=jgyao1@gmail.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