linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-block@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
Date: Mon, 19 Aug 2019 23:37:09 +0500	[thread overview]
Message-ID: <20190819233709.76900bbf@natsu> (raw)
In-Reply-To: <20190819070823.GH12521@merlins.org>

On Mon, 19 Aug 2019 00:08:23 -0700
Marc MERLIN <marc@merlins.org> wrote:

> > Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
> > Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
> > Default Access Policy: Read/Write
> > Current Access Policy: Read/Write
> > Disk Cache Policy   : Disabled

So does it have a BBU? (Battery backup unit)

> I tried to disable the card's write cache to let linux and its 32GB of
> RAM, do it better, but I didn't see a real improvement:

I'd expect that on the contrary, you should look for ways to enable it, and
force-enable even without that BBU (in case of lack of one), because it feels
like what you did is disable disks' own write buffering, and not (only) the
card's!

What you are observing seems to me like what "dd" does with "oflag=dsync" (and
comparable performance that it gets). Definitely feels like it's in some
"extra safe mode" and, say, every 4KB piece of data leads to full flush to
disk before accepting to write the next 4KB.

More things to try, check if it's possible to set up disks not as 1-member
RAID0, but 1-member "linear" ("JBOD"), or even 1-member RAID1, who knows maybe
some of this would work better.

-- 
With respect,
Roman

  parent reply	other threads:[~2019-08-19 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  7:08 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod Marc MERLIN
2019-08-19  9:18 ` Paolo Valente
2019-08-19 12:02   ` Paolo Valente
2019-08-19 16:40   ` Marc MERLIN
2019-08-19 17:05     ` Paolo Valente
2019-08-19 17:26       ` Marc MERLIN
2019-08-19 11:42 ` o1bigtenor
2019-08-19 16:24   ` Marc MERLIN
2019-08-20  5:49   ` Marc MERLIN
2019-08-19 18:37 ` Roman Mamedov [this message]
2019-08-19 19:16   ` Marc MERLIN

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=20190819233709.76900bbf@natsu \
    --to=rm@romanrm.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=marc@merlins.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).