From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM & high system load
Date: Wed, 2 May 2001 11:08:56 +0000 [thread overview]
Message-ID: <20010502110856.A30791@sistina.com> (raw)
In-Reply-To: <200105012325.RAA27700@lynx.turbolabs.com>; from adilger@turbolinux.com on Tue, May 01, 2001 at 05:25:36PM -0600
On Tue, May 01, 2001 at 05:25:36PM -0600, Andreas Dilger wrote:
> Dominique Larchey writes:
> > I point out that /dev/mmedia/music resides on /dev/hda5
> >
> > time dd if=/dev/mmedia/music of=/dev/null bs=512
> > count=200000 0m37.113s
> > time dd if=/dev/hda5 of=/dev/null bs=512
> > count=200000 0m35.437s
>
> LVM shows 4.7% overhead. This is not so great.
>
> > Ok I am ridiculous ... this has nothing to do with LVM.
> > It has to do with DMA set off by default by linux 2.4.
> > This is the reason of poor IO perf. and CPU eating.
> >
> > After DMA is set on,
> >
> > time dd if=/dev/mmedia/music of=/dev/null bs=512
> > count=200000 0m12.934s
> > time dd if=/dev/hda5 of=/dev/null bs=512
> > count=200000 0m12.110s
>
> Good news - not an LVM problem. Bad news - LVM shows 6.8% overhead.
Did nothing else produce io load while the test on the LV was running?
Did you repeat tests in order to get statistic certainty?
>
> > Perhaps poor perf. for the other person is also DMA related ?-)
>
> No, the other person has drastically different performance with LVM for
> 512-byte I/O compared to raw disk. For 64k-byte I/O performance on LVM
> and raw disk are the same. I _suppose_ that if I/O is done in small
> chunks that PIO mode will have more overhead. Maybe worth asking if
> CPU is high when he is doing 512-byte I/Os.
Yep.
>
> Cheers, Andreas
> --
> Andreas Dilger Turbolinux filesystem development
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-02 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 12:40 [linux-lvm] LVM & high system load Dominique LARCHEY-WENDLING
2001-05-01 15:32 ` Dominique LARCHEY-WENDLING
2001-05-01 16:18 ` Andreas Dilger
2001-05-01 21:50 ` Dominique LARCHEY-WENDLING
2001-05-01 23:25 ` Andreas Dilger
2001-05-02 11:08 ` Heinz J. Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-01 16:05 S. Michael Denton
2001-05-01 21:28 ` Dominique LARCHEY-WENDLING
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=20010502110856.A30791@sistina.com \
--to=mauelshagen@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 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).