All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] mirror_region_size default: 4096 six times faster than 512?
Date: Tue, 21 Feb 2012 10:29:32 -0600	[thread overview]
Message-ID: <20120221102932.19eb3218@bettercgi.com> (raw)

Moving several terabytes of data, I was again struck by the very 
large difference in performance between copying data in small chunks
for large chunks. After seeing larger block sizes make dd eight times
faster, I tried increasing mirror_region_size in lvm.conf:

pvmove with default mirror_region_size of 512: ~4-6 MB/s
pvmove with increased mirror_region_size of 4096: ~22-32 MB/s

Although this was somewhat unscientific testing, I'm quite curious 
what results others get on their hardware. The effect was most 
pronounced for me on a system with a 9550SX-12. I'll do some testing 
on a 8888ELP next week.

If 4096 is OFTEN several times faster than 512, would it make sense 
to consider canging the default?
-- 
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php

             reply	other threads:[~2012-02-21 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21 16:29 Ray Morris [this message]
2012-02-21 16:50 ` [linux-lvm] mirror_region_size default: 4096 six times faster than 512? Alasdair G Kergon
2012-02-21 17:01 ` Les Mikesell
2012-02-23 16:46   ` Ray Morris
2012-02-24 15:57     ` Les Mikesell
2012-02-27 20:40       ` Ray Morris

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=20120221102932.19eb3218@bettercgi.com \
    --to=support@bettercgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.