From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and *bad* performance (no striping)
Date: Tue, 15 May 2001 13:13:57 +0100 [thread overview]
Message-ID: <20010515131357.D524@tykepenguin.com> (raw)
In-Reply-To: <m2n18eygvs.fsf@isnogud.escape.de>; from urs@isnogud.escape.de on Tue, May 15, 2001 at 01:46:15PM +0200
On Tue, May 15, 2001 at 01:46:15PM +0200, Urs Thuermann wrote:
>
> And am I really the only one who sees this? I would really be
> interested to hear from some more people about performance for their
> LVM.
I think one problem is that your "benchmarks" are not very realistic. In
real world use the overhead of LVM is very small. I would respectfully suggest
that you try something like bonnie++ before getting too worried about the
performance of LVM on your machine - unless you spend most of your day doing
"dd" to your disks :-)
Here are some bonnie++ benchmarks of a disk partition and and LV (same disk)
using reiserfs* on my machine:
Disk Partition:
Version 1.00g ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
tyke 496M 10462 98 20675 53 7699 20 11707 96 17808 16 257.0 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 8426 100 +++++ +++ 12622 100 8031 100 +++++ +++ 9635 100
Logical Volume:
Version 1.00g ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
tyke 496M 10577 100 20631 52 7739 20 11676 96 17622 17 260.7 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 8521 100 +++++ +++ 12661 99 8007 100 +++++ +++ 9555 99
patrick
* ext2 is comparable, just the numbers are different.
next prev parent reply other threads:[~2001-05-15 12:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 15:44 [linux-lvm] LVM and *bad* performance (no striping) Urs Thuermann
2001-02-26 20:39 ` Joe Thornber
2001-02-26 21:03 ` Jorg de Jong
2001-02-26 21:38 ` Rik van Riel
2001-02-27 8:35 ` Patrick Caulfield
2001-02-27 12:21 ` Urs Thuermann
2001-02-28 11:05 ` Heinz J. Mauelshagen
2001-04-10 19:30 ` Urs Thuermann
2001-04-10 21:37 ` Andreas Dilger
2001-04-11 11:23 ` Urs Thuermann
2001-04-11 19:49 ` Andreas Dilger
2001-04-11 22:00 ` Terje Kvernes
2001-05-15 11:46 ` Urs Thuermann
2001-05-15 12:13 ` Patrick Caulfield [this message]
2001-05-26 11:17 ` Urs Thuermann
2001-05-27 7:47 ` Andreas Dilger
2001-05-27 9:47 ` Urs Thuermann
2001-05-27 17:01 ` [linux-lvm] LVM and *bad* performance (counterexample) idsfa
2001-05-15 17:08 ` [linux-lvm] LVM and *bad* performance (no striping) Andreas Dilger
2001-05-26 11:23 ` Urs Thuermann
2001-02-26 21:41 ` Rik van Riel
2001-02-27 10:33 ` Urs Thuermann
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=20010515131357.D524@tykepenguin.com \
--to=caulfield@sistina.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 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.