From: "BO MOON" <bmoon@anthologysolutions.com>
To: linux-raid@vger.kernel.org
Subject: Raid0 or Raid1 READ performance
Date: Thu, 16 Dec 2004 13:49:53 -0800 [thread overview]
Message-ID: <000401c4e3b9$2cef1f20$040a10ac@asitest> (raw)
Hi,
I tested and measured the Copy performance using "time cp".
My system Config: Redhat9.0, RocketRAID404 HPT374 card,
Hdd1 ---> /mnt/disk1
Hdd2, Hdd3, Hdd4 --> RAID0 : /mnt/disk2
OR
Hdd1 ------> /mnt/disk1
Hdd3, Hdd4 --> RAID1 : /mnt/disk2
I got the almost same performance on WRITE( disk1 --> disk2) and
READ ( disk2 -> disk1).
EX: >time cp disk1/2gfile disk2, >time cp disk2/2gfile disk1
I am expecting the faster performance on READ than WRITE because of
parallel read from disks more than 2(2 for RAID1, 3 for RAID0) at the
same time.
I heard that old linux ide driver did not support this parallelism but
must be fixed by now(linux2.4.20 or greater).
Any suggestion or opinion?
Thanks,
Bo
next reply other threads:[~2004-12-16 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 21:49 BO MOON [this message]
2004-12-16 22:48 ` Raid0 or Raid1 READ performance Mark Hahn
2004-12-17 4:24 ` BO MOON
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='000401c4e3b9$2cef1f20$040a10ac@asitest' \
--to=bmoon@anthologysolutions.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