From: Dave Olien <dmo@osdl.org>
To: thornber@redhat.com
Cc: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 stripe performance
Date: Mon, 5 Apr 2004 14:29:19 -0700 [thread overview]
Message-ID: <20040405212919.GA12443@osdl.org> (raw)
I'm running tiobench on an LVM2 striped logical volume. I'm comparing
the LVM2 striping performance with a similar striping configuration
using a hardware RAID controller.
With hardware RAID, I'm able to get about 66 megabytes per second on
sequential writes, and 52 megabytes per second with random writes.
With LVM2, I can get only 23 megabytes per second with either random
or sequential writes.
Read performance on LVM is about 10% less than with hardware RAID.
e.g. with 48 threads, hardware RAID sequental reads are 105 megabytes
per second, LVM2 RAID sequential reads are 95 megabytes per second.
This is using an ext2 file system, mounted with noatime.
I think I recall seeing email with similar problems to this on this
mail list. If I recall, the cause had to do with ordering of requests
submitted to disk.
Has there been any work to address this?
Thanks!
Dave Olien
next reply other threads:[~2004-04-05 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 21:29 Dave Olien [this message]
2004-04-06 7:07 ` [linux-lvm] Re: LVM2 stripe performance thornber
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=20040405212919.GA12443@osdl.org \
--to=dmo@osdl.org \
--cc=linux-lvm@redhat.com \
--cc=thornber@redhat.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