From: Stephen Samuel <samuel@bcgreen.com>
To: lonely wolf <wolfy@pcnet.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: disk transfer speed problem
Date: Thu, 28 Feb 2002 14:48:34 -0800 [thread overview]
Message-ID: <3C7EB3C2.5090401@bcgreen.com> (raw)
In-Reply-To: <3C7D4666.6D35B124@pcnet.ro>
Picking nits, perhaps -- but after giving us data on hdc,
you did the test on hdd. I realize you said that it is identical
for both, but if you missed something critical, we'll never see it.
lonely wolf wrote:
> initial data: one brand new intel bonham motherboard (i815) , 900 MHz
> celeron processor
> 2 new 80 GB Seagate Barracuda used as raid1, 7200 RPM,ext3 filesystem,
> RedHat 2.4.9-21 kernel from RH 7.2 updates.
>
> settings (identical for hdc and hdd), as detected by the kernel (except
> for I/O support = 3):
> #hdparm /dev/hdc
> multcount = 16 (on)
> I/O support = 3 (32-bit w/sync)
> unmaskirq = 0 (off)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> nowerr = 0 (off)
> readonly = 0 (off)
> readahead = 8 (on)
> geometry = 23989/16/63, sectors = 156301488, start = 0
>
> #hdparm -i /dev/hdc
>
> Model=ST380021A, FwRev=3.05, SerialNo=3HV080KH
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=156301488
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
>
> #dmesg|grep UDMA
> hda: 14668290 sectors (7510 MB) w/418KiB Cache, CHS=913/255/63, UDMA(66)
> (this is the boot disk)
>
> hdc: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63,
> UDMA(100
> hdd: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63,
> UDMA(100)
>
> The IDE cables have 80 wires. I am not sure that they are ATA100, but I
> think they do.
>
> The problem:
> #/sbin/hdparm -tTf /dev/hdd
>
> /dev/hdd:
> Timing buffer-cache reads: 128 MB in 1.17 seconds =109.40 MB/sec
> Timing buffered disk reads: 64 MB in 3.24 seconds = 19.75 MB/sec
>
>
> Even after issuing raidstop and umounting the partition placed on the
> RAID, the speed does not exceed 22 MB/sec.
>
> With hdparm -c1 performances are almost identical
>
> Tests were performed in initlevel 3, with NFS started, but no one but
> root using the machine (from console). In production, the speed is also
> very, very slow
>
> Any idea what might limit the transfer speed ?
>
>
> --
> Manuel Wolfshant linux registered user #131416
> network administrator NoBug Consulting Romania
> Beware the fury of a patient man.
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.
next prev parent reply other threads:[~2002-02-28 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 20:49 disk transfer speed problem lonely wolf
2002-02-28 2:06 ` Tim Moore
2002-02-28 4:51 ` Andre Hedrick
2002-02-28 11:56 ` Dave Jones
2002-02-28 17:14 ` Andre Hedrick
2002-02-28 12:27 ` Martin Dalecki
2002-02-28 22:48 ` Stephen Samuel [this message]
2002-02-28 23:58 ` lonely wolf
[not found] <Pine.LNX.4.33.0202271701360.13103-100000@coffee.psychology.mcmaster.ca>
2002-02-27 22:52 ` lonely wolf
2002-02-27 23:46 ` Alan Cox
2002-02-28 9:20 ` Davidovac Zoran
2002-02-28 14:49 ` lonely wolf
2002-03-01 2:25 ` lonely wolf
2002-03-01 10:59 ` Andre Hedrick
2002-03-01 10:51 ` Marco Colombo
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=3C7EB3C2.5090401@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wolfy@pcnet.ro \
/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.