From: Werner John <john@oswf.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Horrid performance with 2.4.{9,10,12} + LVM + ReiserFS
Date: Thu, 18 Oct 2001 11:17:43 +0200 [thread overview]
Message-ID: <15310.40503.356813.663284@rigel.oswf.de> (raw)
In-Reply-To: <20011018000006.A22777@jensbenecke.de>
Jens Benecke writes:
> Hello,
Hello,
> this is CC'ed to LVM user list and ReiserFS because I don't know who to
> blame currently. ;)
>
lets, see ...
>
> I have severe performance problems with a 210G ReiserFS volume sitting on a
> LVM (1.0.1rc4) spread over three disks (Maxtor 60, 80, 80GB IDE). The
> system is a Duron 650MHz with via686b chipset and UDMA-100 capable IDE.
> /proc/cpuinfo, /proc/ide/via output see below. The hardware seems
> performant enough to me.
> [...]
>
> ---------------------------------------------------------------------------
> hdparm output for the three disks:
>
> server: /home# hdparm -tT /dev/hd[abcd]
> /dev/hda:
> Timing buffer-cache reads: 128 MB in 0.86 seconds =148.84 MB/sec
> Timing buffered disk reads: 64 MB in 2.12 seconds = 30.19 MB/sec
> /dev/hdc:
> Timing buffer-cache reads: 128 MB in 0.84 seconds =152.38 MB/sec
> Timing buffered disk reads: 64 MB in 2.28 seconds = 28.07 MB/sec
> /dev/hdd:
> Timing buffer-cache reads: 128 MB in 0.86 seconds =148.84 MB/sec
> Timing buffered disk reads: 64 MB in 2.36 seconds = 27.12 MB/sec
Well, you have 1 disk on a single channel (hda) and the other two as master
and slave on *one* channel. That's the bottleneck. If the disks are
accessed individually, you get the full performance (more or less). But if
*both* disks have to respond, performance drops horribly.
Best is to get a third IDE controller.
Yours,
Werner
>
>
> bonnie++ output for the LVM volume: ---------------------------------------
> Version 1.01d ------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
> server 256M 5596 97 24539 34 6926 7 5194 87 24662 17 115.1 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 7965 99 +++++ +++ 10546 99 5458 92 +++++ +++ 8214 90
> server,256M,5596,97,24539,34,6926,7,5194,87,24662,17,115.1,1,16,7965,99,+++++,++
> ---------------------------------------------------------------------------
>
>
>
>
> --
> Jens Benecke ииииииии http://www.hitchhikers.de/ - Europas Mitfahrzentrale
>
> Crypto regulations will only hinder criminals who obey the law.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
next prev parent reply other threads:[~2001-10-18 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011018000006.A22777@jensbenecke.de>
2001-10-17 22:30 ` [linux-lvm] Re: [reiserfs-list] Horrid performance with 2.4.{9,10,12} + LVM + ReiserFS Andreas Dilger
2001-10-17 23:00 ` Hans Reiser
2001-10-18 0:48 ` [linux-lvm] " José Luis Domingo López
2001-10-18 9:17 ` Werner John [this message]
[not found] ` <20011019030045.O25054@jensbenecke.de>
2001-10-19 1:19 ` Eric M. Hopper
2001-10-19 5:49 ` Werner John
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=15310.40503.356813.663284@rigel.oswf.de \
--to=john@oswf.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 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).