From: Andreas Peter <ujq7@rz.uni-karlsruhe.de>
To: linux-kernel@vger.kernel.org
Subject: Re: SW-RAID0 Performance problems
Date: Sat, 14 Apr 2001 12:45:07 +0200 [thread overview]
Message-ID: <01041412085801.00516@debian> (raw)
In-Reply-To: <Pine.LNX.4.10.10104131048550.1669-100000@coffee.psychology.mcmaster.ca> <20010413090751.E4557@greenhydrant.com> <3AD7416A.A6B65A86@bigfoot.com>
In-Reply-To: <3AD7416A.A6B65A86@bigfoot.com>
Am Freitag, 13. April 2001 20:11 schrieb Tim Moore:
> Try 'hdparm -tT' with simultaneous /dev/hda3 and /dev/hdc3. This gives
> you a baseline on the actual partitions involved.
hdparm -tT simultanous on /dev/hda3 and /dev/hdc3:
/dev/hda3:
Timing buffer-cache reads: 128 MB in 2.29 seconds = 55.90 MB/sec
Timing buffered disk reads: 64 MB in 4.67 seconds = 13.70 MB/sec
/dev/hdc3:
Timing buffer-cache reads: 128 MB in 2.28 seconds = 56.14 MB/sec
Timing buffered disk reads: 64 MB in 4.61 seconds = 13.88 MB/sec
Now on single HD - /dev/hda3 :
/dev/hda3:
Timing buffer-cache reads: 128 MB in 1.30 seconds = 98.46 MB/sec
Timing buffered disk reads: 64 MB in 2.26 seconds = 28.32 MB/sec
It looks like reading on /dev/hda3 locks /dev/hdc3 ...
Is it necessary to apply the ide-patches to the kernel ?
Andreas
--
Andreas Peter *** ujq7@rz.uni-karlsruhe.de
next prev parent reply other threads:[~2001-04-14 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10104131048550.1669-100000@coffee.psychology.mcmaster.ca>
2001-04-13 15:36 ` SW-RAID0 Performance problems Andreas Peter
2001-04-13 16:07 ` David Rees
2001-04-13 16:28 ` Andreas Peter
2001-04-14 7:04 ` David Rees
2001-04-14 9:38 ` Andreas Peter
2001-04-14 12:28 ` Kurt Roeckx
2001-04-14 13:09 ` Andreas Peter
2001-04-13 18:11 ` Tim Moore
2001-04-14 10:45 ` Andreas Peter [this message]
2001-04-13 11:47 Andreas Peter
2001-04-13 16:01 ` Jakob Østergaard
2001-04-13 16:28 ` Andreas Peter
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=01041412085801.00516@debian \
--to=ujq7@rz.uni-karlsruhe.de \
--cc=linux-kernel@vger.kernel.org \
/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.