Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: David Hajes <d.hajes29a@pm.me>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: RAID 5, 10 modern post 2020 drives, slow speeds
Date: Sat, 8 Mar 2025 01:47:18 +0500	[thread overview]
Message-ID: <20250308014718.24418feb@nvm> (raw)
In-Reply-To: <CAAMCDefMK6PD7+BpfQ9e2WGjdsk_hQaoGOAYmQ2_Rtn5o7nGrQ@mail.gmail.com>

On Fri, 7 Mar 2025 14:42:24 -0600
Roger Heflin <rogerheflin@gmail.com> wrote:

> I put an external bitmap on a raid1 SSD and that seemed to speed up my
> writes.  I am not sure if external bitmaps will continue to be
> supported as I have seen notes that I don't exactly understand for
> external bitmaps, and I have to reapply the external bitmap on each
> reboot for my arrays which has some data loss risks in a crash case
> with a dirty bitmap.
> 
> This is the command I used to set it up.
> mdadm --grow --force --bitmap=/mdraid-bitmaps/md15-bitmap.img /dev/md15

In this case the result cited seems to have shown the bitmap is not the issue.

I remember seeing patches or talks to remove external bitmap support, too.

In my experience the internal bitmap with a large enough chunk size does not
slow down the write speed that much. Try a chunk size of 256M. Not sure how
high it's worth going before the benefits diminish.

-- 
With respect,
Roman

  reply	other threads:[~2025-03-07 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 18:36 RAID 5, 10 modern post 2020 drives, slow speeds David Hajes
2025-03-07 18:47 ` Roman Mamedov
2025-03-07 19:25   ` David Hajes
2025-03-07 20:42     ` Roger Heflin
2025-03-07 20:47       ` Roman Mamedov [this message]
2025-03-08 17:59         ` David Hajes
2025-03-12 21:09           ` David Hajes
     [not found]             ` <CALtW_ajQimm6duqkmyWbBL3MKZ9yC5Prxj=eE9vW9+pTQ=+7Eg@mail.gmail.com>
     [not found]               ` <mUTk9RKcp55IgkOLdK7prUD52e30aOJ1sQNoTaedBafMvGRVR1TxZnnBFQADU3BVc1AUfps0lsv_e9wG8PxnpXqpWt-UYKHwksp6M1b7sDU=@pm.me>
2025-03-13  6:39                 ` Fw: " David Hajes
2025-03-30  6:25 ` Xiao Ni

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=20250308014718.24418feb@nvm \
    --to=rm@romanrm.net \
    --cc=d.hajes29a@pm.me \
    --cc=linux-raid@vger.kernel.org \
    --cc=rogerheflin@gmail.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