All of lore.kernel.org
 help / color / mirror / Atom feed
From: Urs Thuermann <urs@isnogud.escape.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LVM and *bad* performance (no striping)
Date: 26 Feb 2001 16:44:34 +0100	[thread overview]
Message-ID: <m2snl1phy5.fsf@isnogud.escape.de> (raw)

I tried to use LVM today using Linux 2.4.2 and it mostly works like I
expected.  But the performance is unacceptably bad:

    isnogud:/root# fdisk -l /dev/sda|grep sda5
    /dev/sda5            80       399   2570368+  8e  Linux LVM
    isnogud:/root# pvcreate /dev/sda5
    pvcreate -- physical volume "/dev/sda5" successfully created
    
    isnogud:/root# vgcreate vg0 /dev/sda5
    vgcreate -- INFO: using default physical extent size 4 MB
    vgcreate -- INFO: maximum logical volume size is 255.99 Gigabyte
    vgcreate -- doing automatic backup of volume group "vg0"
    vgcreate -- volume group "vg0" successfully created and activated
    
    isnogud:/root# lvcreate -n test /dev/vg0 -L 300M
    lvcreate -- doing automatic backup of "vg0"
    lvcreate -- logical volume "/dev/vg0/test" successfully created
    
    isnogud:/root# time dd if=/dev/sda5 of=/dev/null count=100000
    100000+0 records in
    100000+0 records out
    
    real    0m6.720s
    user    0m0.300s
    sys     0m0.970s
    isnogud:/root# time dd if=/dev/vg0/test of=/dev/null count=100000
    100000+0 records in
    100000+0 records out
    
    real    0m41.851s
    user    0m0.350s
    sys     0m2.250s

When making an ext2 filesystem on /dev/sda5 or /dev/vg0/test
respectivley, the performance of cp'ing, grep'ing all files and rm'ing
all files, seems to be comparable.  But why is the performance of
reading the block device with dd so bad?


urs

             reply	other threads:[~2001-02-26 15:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 15:44 Urs Thuermann [this message]
2001-02-26 20:39 ` [linux-lvm] LVM and *bad* performance (no striping) 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
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=m2snl1phy5.fsf@isnogud.escape.de \
    --to=urs@isnogud.escape.de \
    --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.