All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Kks Kbase <kks.kbase@yahoo.in>, Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Know about chunk size
Date: Mon, 26 Nov 2012 16:11:34 -0600	[thread overview]
Message-ID: <50B3E916.90205@hardwarefreak.com> (raw)
In-Reply-To: <186704.2.1353915309639.JavaMail.root@zimbra>

On 11/26/2012 1:35 AM, Roy Sigurd Karlsbakk wrote:
>> I want to know what is best chunk size to create s/w raid devices?
> 
> That depends on the workload, file sizes etc. 

Correct.  And greatly depends on array type.

> The default will probably do fine

This is not true of metadata 1.2 and parity arrays in which case the
default chunk size is 512KB.  That's way too large for anything but
large file streaming workloads.  Most workloads involve metadata and
small files.  This has been discussed previously in detail on this list
and on the XFS list.  For most workloads other than large file
streaming, mirroring+striping is best, but if you must use parity RAID a
small chunk size of 32/64KB yields superior IO performance due to
decreased overhead during RMW.

>> Also is it possible to change the chunk size for an existing array?

No.  You must destroy and recreate it with the new chunk size.  If one
creates an array with an appropriate chunk size there is no need to ever
change it, UNLESS the primary workload hitting the array changes from
random IO to large streaming, or the reverse.  In such a case one
typically builds a new server with a new array, or simply adds a new
array to the existing server for the new workload.  If you are
redeploying the server/array, destroy and recreate with the new optimal
chunk size.

-- 
Stan


  reply	other threads:[~2012-11-26 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25  3:15 Know about chunk size Kks Kbase
2012-11-26  7:35 ` Roy Sigurd Karlsbakk
2012-11-26 22:11   ` Stan Hoeppner [this message]
2012-11-27  7:39     ` Kks Kbase
2012-11-27  8:19       ` Roy Sigurd Karlsbakk
2012-11-27 18:36       ` Piergiorgio Sartor

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=50B3E916.90205@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=kks.kbase@yahoo.in \
    --cc=linux-raid@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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.