From: idsfa@visi.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] What is a good stripe size?
Date: Sun, 17 Jun 2001 13:44:43 -0500 [thread overview]
Message-ID: <20010617134443.A240@mitethe.eudyptes> (raw)
In-Reply-To: <m23d90imdv.fsf@isnogud.escape.de>; from urs@isnogud.escape.de on Sat, Jun 16, 2001 at 03:29:16PM +0200
On Sat, Jun 16, 2001 at 03:29:16PM +0200, Urs Thuermann wrote:
> Using the PVs on sda2 and sdb2 I created a single VG and I want to
> create striped LVs on it now. My questions is, how large should I
> choose the stripe size to achive optimal performance. If I choose it
> too large, I will probably loose the win of striping.
You lose the advantage of striping if the stripe size is on the order
of the file size. You want stripes which will be narrower than most
of the files you will be using.
The ideal stripe size is a multiple of the size of the blocks in the
filesystem. Reads and writes work most efficiently when they can
run a block at a time, rather than having to buffer up fragments.
These two guidelines usually leave you with a stripe which is between
1-4x your block size.
If you do not know the size of the blocks in your filesystem, there
is usually a filesystem tool which will tell you (dumpe2fs for ext2,
debugreiserfs for reiser, etc etc).
Ex. My machine has only reiserfs. debugreiserfs tells me that the
filesystems use 4096 byte blocks. I therefore have 4096-byte
wide stripes. This also accomodates ext2 (block sizes can be
between 1024-4096) and most of the other available filesystems,
which use multiples of 1k. It is a little wide for those which
use 512 byte blocks, but I am unlikely to use such an obsolete
fs for anything speed critical.
--
$ fortune -m Kellen
next prev parent reply other threads:[~2001-06-17 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-16 13:29 [linux-lvm] What is a good stripe size? Urs Thuermann
2001-06-17 18:44 ` idsfa [this message]
[not found] <134933704.992803570667.JavaMail.root@boots>
2001-06-17 21:36 ` Wolfgang Weisselberg
2001-06-17 23:13 ` Steven Lembark
2001-06-18 10:04 ` Heinz J. Mauelshagen
2001-06-18 4:07 ` idsfa
[not found] <134718885.992837796416.JavaMail.root@boots>
2001-06-18 10:33 ` Wolfgang Weisselberg
2001-06-21 8:46 ` Joe Thornber
2001-06-22 0:59 ` Wolfgang Weisselberg
2001-06-22 9:49 ` Joe Thornber
2001-06-22 14:25 ` Heinz J. Mauelshagen
[not found] <134782415.992819826651.JavaMail.root@boots>
2001-06-18 11:19 ` Wolfgang Weisselberg
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=20010617134443.A240@mitethe.eudyptes \
--to=idsfa@visi.com \
--cc=linux-lvm@sistina.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