From: Jay Strauss <me@heyjay.com>
To: linux-raid@vger.kernel.org
Subject: Raid 1 install revealed poor HD performance (I think)
Date: Tue, 17 May 2005 10:11:31 -0500 [thread overview]
Message-ID: <428A09A3.9000802@heyjay.com> (raw)
Hi,
I just installed a simple raid-1. I have a single HD on each
controller. ie. 2 controllers 2 HDs. That's it, no CD players or DVD
drives...
I did a fresh install of Sarge. After reboot I unplugged the CD drive,
and let the array sync overnight. It took 10hrs to sync 160GiB, which
seemed pretty long, so I executed the "dd if=/dev/hda of=/dev/null
bs=64k count=10000" command I've seen posted on this list.
It took about a minute and change to complete, which is long. So out of
curiosity I plugged in a CD player and booted Knoppix. When I ran the
same command it took only 30 seconds (which is still not as quick as
some of the numbers on this list, but it's an old celeron 466MHz).
I'm very unfamiliar with options for speeding up hard drive access.
What might Knoppix be setting (and how would I look for it), that it's
getting 100% better drive performance than a plain jane Sarge install?
Thanks
Jay
******** Knoppix Run ***********
root@ttyp0[~]# for i in 1 2 3; do
> time dd if=/dev/hda of=/dev/null bs=64k count=10000
> done
10000+0 records in
10000+0 records out
655360000 bytes transferred in 46.301872 seconds (14154071 bytes/sec)
real 0m46.754s
user 0m0.480s
sys 0m29.710s
10000+0 records in
10000+0 records out
655360000 bytes transferred in 49.852186 seconds (13146063 bytes/sec)
real 0m51.075s
user 0m0.430s
sys 0m26.610s
10000+0 records in
10000+0 records out
655360000 bytes transferred in 46.237684 seconds (14173720 bytes/sec)
real 0m47.928s
user 0m0.480s
sys 0m31.770s
************** Sarge Run *************
sandy:~# for i in 1 2 3; do
> time dd if=/dev/hda of=/dev/null bs=64k count=10000
> done
10000+0 records in
10000+0 records out
655360000 bytes transferred in 66.004525 seconds (9929016 bytes/sec)
real 1m6.052s
user 0m0.637s
sys 1m2.888s
10000+0 records in
10000+0 records out
655360000 bytes transferred in 63.797226 seconds (10272547 bytes/sec)
real 1m3.886s
user 0m0.678s
sys 1m0.732s
10000+0 records in
10000+0 records out
655360000 bytes transferred in 64.729628 seconds (10124575 bytes/sec)
real 1m4.822s
user 0m0.616s
sys 1m1.668s
next reply other threads:[~2005-05-17 15:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 15:11 Jay Strauss [this message]
2005-05-17 15:50 ` Raid 1 install revealed poor HD performance (I think) Gordon Henderson
2005-05-17 16:17 ` Jay Strauss
2005-05-17 16:23 ` Gordon Henderson
2005-05-17 16:52 ` Mike Hardy
2005-05-17 20:51 ` Jay Strauss
2005-05-17 20:54 ` Mike Hardy
2005-05-17 22:16 ` Tobias Hofmann
2005-05-17 23:00 ` Jay Strauss
2005-05-18 3:28 ` Jay Strauss
2005-05-17 22:45 ` Peter T. Breuer
2005-05-17 23:42 ` Henrik Holst
2005-05-18 3:30 ` Jay Strauss
2005-05-17 23:44 ` Henrik Holst
2005-05-19 15:32 ` Jay Strauss
2005-05-19 16:14 ` Mike Hardy
2005-05-19 18:40 ` Jay Strauss
2005-05-19 20:43 ` Mike Hardy
2005-05-20 1:43 ` Jay Strauss
[not found] <Pine.LNX.4.44.0505180206580.1777-100000@coffee.psychology.mcmaster.ca>
2005-05-18 15:08 ` Mike Hardy
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=428A09A3.9000802@heyjay.com \
--to=me@heyjay.com \
--cc=linux-raid@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 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).