linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin T <m4rtntns@gmail.com>
To: stan@hardwarefreak.com
Cc: "linux-raid@vger.kernel.org List" <linux-raid@vger.kernel.org>
Subject: Re: calculating optimal chunk size for Linux software-RAID
Date: Sat, 8 Mar 2014 03:15:38 +0000	[thread overview]
Message-ID: <CAJx5YvH1GE0KUcsSnVwbtUz6qP4zMv3N2qt3HhrjdF69NT2vLQ@mail.gmail.com> (raw)
In-Reply-To: <531A5D2F.3010002@hardwarefreak.com>

Stan,

ok, I see. However, are there utilities out there which help one to
analyze how applications on a server use the file-system over the time
and help to make an educated decision regarding the chunk size?


regards,
Martin

On Fri, Mar 7, 2014 at 11:58 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> On 3/6/2014 8:06 PM, Martin T wrote:
>> Am I correct that optimal chunk size is usually the size of the
>> average file read/written to disk divided by number of block devices
>> in RAID array storing the data? For example if the average file size
>> is 1024KiB and I have four disks in RAID1, then I should choose the
>> chunk size around 256KiB to get the optimal read performance? Or if I
>> have two drives in RAID0, then I should choose the chunk size 512KiB
>> instead? Or are there better methods/benchmarks to determine the
>> optimal chunk size for software-RAID?
>
> You're asking the wrong question.  Storage architecture design always
> begins with the workload.  The correct question is:
>
> My workload (application mix) performs *most* IO in manner X, where X is
>
> 1.  large streaming write/read
> 2.  small file write/read
> 3.  metadata heavy
>
> I have Y number of disk drives.  I plan to use XFS/EXT4/etc filesystem.
>  What RAID level and chunk size are optimal for my workload, and how do
> I properly tune my filesystem to my workload and storage stack?
>
>> Last but not least, is there a
>> good utility which could help one to measure the average I/O
>> read/write size?
>
> In flight IO size has no correlation to stripe and chunk size.  What you
> need to know is how your application(s) write to the filesystem and how
> your filesystem issues write IOs.  You should already know that the
> former, and it's easy to determine the latter.
>
> --
> Stan

  reply	other threads:[~2014-03-08  3:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  2:06 calculating optimal chunk size for Linux software-RAID Martin T
2014-03-07 23:58 ` Stan Hoeppner
2014-03-08  3:15   ` Martin T [this message]
2014-03-08  5:37     ` Stan Hoeppner
2014-03-08 22:03       ` Bill Davidsen
2014-03-12 15:21         ` Martin T
2014-03-13 10:15           ` Stan Hoeppner

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=CAJx5YvH1GE0KUcsSnVwbtUz6qP4zMv3N2qt3HhrjdF69NT2vLQ@mail.gmail.com \
    --to=m4rtntns@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=stan@hardwarefreak.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;
as well as URLs for NNTP newsgroup(s).