linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	John Stoffel <john@stoffel.org>
Subject: Re: [linux-lvm] Best way to run LVM over multiple SW RAIDs?
Date: Mon, 9 Dec 2019 11:40:22 +0100	[thread overview]
Message-ID: <6399a003-cec7-dcc0-656d-0a4c577ce4bf@cloud.ionos.com> (raw)
In-Reply-To: <24044.11058.338208.602498@quad.stoffel.home>



On 12/7/19 11:44 PM, John Stoffel wrote:
>>>>>> "Stuart" == Stuart D Gathman<stuart@gathman.org>  writes:
> Stuart> On Tue, Oct 29, 2019 at 12:14 PM Daniel Janzon<daniel.janzon@edgeware.tv>  wrote:
>>> I have a server with very high load using four NVMe SSDs and
>>> therefore no HW RAID. Instead I used SW RAID with the mdadm tool.
>>> Using one RAID5 volume does not work well since the driver can only
>>> utilize one CPU core which spikes at 100% and harms performance.
>>> Therefore I created 8 partitions on each disk, and 8 RAID5s across
>>> the four disks.
>>> Now I want to bring them together with LVM. If I do not use a striped
>>> volume I get high performance (in expected magnitude according to disk
>>> specs). But when I use a striped volume, performance drops to a
>>> magnitude below. The reason I am looking for a striped setup is to
> Stuart> The mdadm layer already does the striping.  So doing it again
> Stuart> in the LVM layer completely screws it up.  You want plain JBOD
> Stuart> (Just a Bunch Of Disks).
>
> Umm... not really.  The problem here is more the MD layer not being
> able to run RAID5 across multiple cores at the same time, which is why
> he split things the way he did.
>
> But we don't know the Kernel version, the LVM version, or the OS
> release so as to give better ideas of what to do.
>
> The biggest harm to performance here is really the RAID5, and if you
> can instead move to RAID 10 (mirror then stripe across mirrors) then
> you should be a performance boost.
>
> As Daniel says, he's got lots of disk load, but plenty of CPU, so the
> single thread for RAID5 is a big bottleneck.

Perhaps set "/sys/block/mdx/md/group_thread_cnt" could help here,
see below commits:

commit b721420e8719131896b009b11edbbd27d9b85e98
Author: Shaohua Li <shli@kernel.org>
Date:   Tue Aug 27 17:50:42 2013 +0800

     raid5: sysfs entry to control worker thread number

commit 851c30c9badfc6b294c98e887624bff53644ad21
Author: Shaohua Li <shli@kernel.org>
Date:   Wed Aug 28 14:30:16 2013 +0800

     raid5: offload stripe handle to workqueue

Thanks,
Guoqing

  parent reply	other threads:[~2019-12-09 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29  8:47 [linux-lvm] Best way to run LVM over multiple SW RAIDs? Daniel Janzon
2019-12-07 16:16 ` Anatoly Pugachev
2019-12-07 17:37   ` Roberto Fastec
2019-12-07 20:34     ` Stuart D. Gathman
2019-12-07 22:44       ` John Stoffel
2019-12-07 23:14         ` Stuart D. Gathman
2019-12-08 11:57           ` Gionatan Danti
2019-12-08 22:51           ` John Stoffel
2019-12-09 10:40         ` Guoqing Jiang [this message]
2019-12-09 10:26 Daniel Janzon
2019-12-09 14:26 ` Marian Csontos
2019-12-10 11:23 ` Gionatan Danti
2019-12-10 21:29   ` John Stoffel
2019-12-16  8:22 Daniel Janzon

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=6399a003-cec7-dcc0-656d-0a4c577ce4bf@cloud.ionos.com \
    --to=guoqing.jiang@cloud.ionos.com \
    --cc=john@stoffel.org \
    --cc=linux-lvm@redhat.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).