From: Paul Clements <paul.clements@steeleye.com>
To: Shane <shane@cm.nu>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 bitmap performance
Date: Thu, 26 Oct 2006 15:40:54 -0400 [thread overview]
Message-ID: <45410F46.4080705@steeleye.com> (raw)
In-Reply-To: <20061026183015.GA20602@cm.nu>
Shane wrote:
> I just thought I'd give internal bitmaps a try using mdadm
> -G -b internal and the write speed:
> dd if=/dev/zero of=test.dat oflag=dsync bs=1024k count=1024
> went from 20mbps to 15mbps. Is that a typical hit for the
> bitmap? I don't resync very often so it may not be
> necessary. Just wondering whether there is anything that
> should be tuned.
You could try tuning the bitmap chunk size. The bitmap chunk size
determines how much data each bit represents, so it determines how often
the bitmap has to be updated when you're writing data to the array. By
default, it's set according to whatever can fit into the space between
the md superblock and the end of the disk (typically 60KB). If you have
small disks, the chunk size will be 4K, and it goes up from there
depending on the size of the disks (typically in the range of 64KB-256KB).
You might try a bitmap chunk size of a megabyte or several megabytes and
see if that improves things. It'll mean less seeking of the disk head to
do the bitmap updates.
--
Paul
parent reply other threads:[~2006-10-26 19:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20061026183015.GA20602@cm.nu>]
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=45410F46.4080705@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=shane@cm.nu \
/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).