linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Billy Crook <billycrook@gmail.com>,
	"Henry, Andrew" <andrew.henry@logica.com>,
	Drew <drew.kay@gmail.com>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: raid-0 with mdadm vs lvm striping
Date: Thu, 13 Aug 2009 10:08:34 +0200	[thread overview]
Message-ID: <20090813080834.GA24883@rap.rap.dk> (raw)
In-Reply-To: <874osc5ut5.fsf@frosties.localdomain>

On Thu, Aug 13, 2009 at 04:09:10AM +0200, Goswin von Brederlow wrote:
> Billy Crook <billycrook@gmail.com> writes:
> 
> > On Wed, Aug 12, 2009 at 04:14, Henry, Andrew<andrew.henry@logica.com> wrote:
> >> That's what my question was:  Will raid0 (striping) be faster or easier to manage than lvm striping
> >
> > LVM striping won't change performance for small files. (That is files,
> > smaller than the extent size.)  To be fair, RAID-0 striping won't
> > accelerate file access for files smaller than the stripe size either.

Have you tested this? In theory, both LVM and raid0 striping should
accellerate access to small files substantially, for example if a
process accesses a number of small files, which are laid out in sequence
on the file system. This is a common case. 

I think this could come about eg if you roll in a tarball or package of
a system, then the small files are created in sequence, and the file
system should lay them out in sequence on the disk. When reading again,
the disk read ahead would secure that most of the data for a number of
small files were already read into the kernel cache when asked for, and
thus the files would be read at striping speeds. 

> > However, traditionally, raid0 stripe sizes are much much smaller than
> > LVM extent sizes.  Both are however adjustable.

What are the parameters? raid normally assumes 64 kiB chunks, but i
normally use 256 kiB chunks, which is the lowest chunk size that we are
recommending out of the linux-raid group. What are normal with LVM?

best regards
keld
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-08-13  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10  7:09 raid-0 with mdadm vs lvm striping Henry, Andrew
2009-08-11 21:35 ` Drew
2009-08-12  6:55   ` Henry, Andrew
2009-08-12  8:41     ` Goswin von Brederlow
2009-08-12  9:14       ` Henry, Andrew
2009-08-12 16:00         ` Billy Crook
2009-08-13  2:09           ` Goswin von Brederlow
2009-08-13  2:40             ` Guy Watkins
2009-08-17  7:27               ` Goswin von Brederlow
2009-08-13  8:08             ` Keld Jørn Simonsen [this message]
2009-08-12 17:47         ` Drew

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=20090813080834.GA24883@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=andrew.henry@logica.com \
    --cc=billycrook@gmail.com \
    --cc=drew.kay@gmail.com \
    --cc=goswin-v-b@web.de \
    --cc=linux-raid@vger.kernel.org \
    /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).