From: Iustin Pop <iusty@k1024.org>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Oliver Martin <oliver.martin@student.tuwien.ac.at>,
Janek Kozicki <janek_listy@wp.pl>,
linux-raid@vger.kernel.org
Subject: Re: LVM performance (was: Re: RAID5 to RAID6 reshape?)
Date: Tue, 19 Feb 2008 21:00:48 +0100 [thread overview]
Message-ID: <20080219200048.GB7693@teal.hq.k1024.org> (raw)
In-Reply-To: <cccedfc60802191152k11f0f093gf26e42ed7d888c6d@mail.gmail.com>
On Tue, Feb 19, 2008 at 01:52:21PM -0600, Jon Nelson wrote:
> On Feb 19, 2008 1:41 PM, Oliver Martin
> <oliver.martin@student.tuwien.ac.at> wrote:
> > Janek Kozicki schrieb:
> >
> > $ hdparm -t /dev/md0
> >
> > /dev/md0:
> > Timing buffered disk reads: 148 MB in 3.01 seconds = 49.13 MB/sec
> >
> > $ hdparm -t /dev/dm-0
> >
> > /dev/dm-0:
> > Timing buffered disk reads: 116 MB in 3.04 seconds = 38.20 MB/sec
>
> I'm getting better performance on a LV than on the underlying MD:
>
> # hdparm -t /dev/md0
>
> /dev/md0:
> Timing buffered disk reads: 408 MB in 3.01 seconds = 135.63 MB/sec
> # hdparm -t /dev/raid/multimedia
>
> /dev/raid/multimedia:
> Timing buffered disk reads: 434 MB in 3.01 seconds = 144.04 MB/sec
> #
As people are trying to point out in many lists and docs: hdparm is
*not* a benchmark tool. So its numbers, while interesting, should not be
regarded as a valid comparison.
Just my oppinion.
regards,
iustin
next prev parent reply other threads:[~2008-02-19 20:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 3:58 RAID5 to RAID6 reshape? Beolach
2008-02-17 11:50 ` Peter Grandi
2008-02-17 14:45 ` Conway S. Smith
2008-02-18 5:26 ` Janek Kozicki
2008-02-18 12:38 ` Beolach
2008-02-18 14:42 ` Janek Kozicki
2008-02-19 19:41 ` LVM performance (was: Re: RAID5 to RAID6 reshape?) Oliver Martin
2008-02-19 19:52 ` Jon Nelson
2008-02-19 20:00 ` Iustin Pop [this message]
2008-02-19 23:19 ` LVM performance Peter Rabbitson
2008-02-20 12:19 ` LVM performance (was: Re: RAID5 to RAID6 reshape?) Peter Grandi
2008-02-22 13:41 ` LVM performance Oliver Martin
2008-03-07 8:14 ` Peter Grandi
2008-03-09 19:56 ` Oliver Martin
2008-03-09 21:13 ` Michael Guntsche
2008-03-09 23:27 ` Oliver Martin
2008-03-09 23:53 ` Michael Guntsche
2008-03-10 8:54 ` Oliver Martin
2008-03-10 21:04 ` Peter Grandi
2008-03-12 14:03 ` Michael Guntsche
2008-03-12 19:54 ` Peter Grandi
2008-03-12 20:11 ` Guntsche Michael
2008-03-10 0:32 ` Richard Scobie
2008-03-10 0:53 ` Michael Guntsche
2008-03-10 0:59 ` Richard Scobie
2008-03-10 1:21 ` Michael Guntsche
2008-02-18 19:05 ` RAID5 to RAID6 reshape? Peter Grandi
2008-02-20 6:39 ` Alexander Kühn
2008-02-22 8:13 ` Peter Grandi
2008-02-23 20:40 ` Nagilum
2008-02-25 0:10 ` Peter Grandi
2008-02-25 16:31 ` Nagilum
2008-02-17 13:31 ` Janek Kozicki
2008-02-17 16:18 ` Conway S. Smith
2008-02-18 3:48 ` Neil Brown
2008-02-17 22:40 ` Mark Hahn
2008-02-17 23:54 ` Janek Kozicki
2008-02-18 12:46 ` Andre Noll
2008-02-18 18:23 ` Mark Hahn
2008-02-17 14:06 ` Janek Kozicki
2008-02-17 23:54 ` cat
2008-02-18 3:43 ` Neil Brown
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=20080219200048.GB7693@teal.hq.k1024.org \
--to=iusty@k1024.org \
--cc=janek_listy@wp.pl \
--cc=jnelson-linux-raid@jamponi.net \
--cc=linux-raid@vger.kernel.org \
--cc=oliver.martin@student.tuwien.ac.at \
/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).