From: Kent Borg <kentborg@borg.org>
To: "Jakob Østergaard" <jakob@unthought.net>,
"Arjan van de Ven" <arjanv@redhat.com>,
"Jaime Medrano" <overflow@eurielec.etsit.upm.es>,
linux-kernel@vger.kernel.org
Subject: Re: raid1 performance
Date: Wed, 1 May 2002 13:01:27 -0400 [thread overview]
Message-ID: <20020501130127.A10936@borg.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0204301411210.4658-100000@cuatro.eurielec.etsit.upm.es> <3CCE9038.F4C830B4@redhat.com> <20020430102148.D4470@borg.org> <20020501183553.D31556@unthought.net>
On Wed, May 01, 2002 at 06:35:53PM +0200, Jakob Østergaard wrote:
> This is *not* as simple as it sounds. Believe me, I spent a week trying...
>
> However, with ext2 (and other filesystems as well), a large sequential file
> read is *not* sequential on the disk. You should actually see better performance
> on RAID-1 than on a single disk for very large reads, becuase some of the lookups
> needed (block indirection or whatever) will be run by the "best" disk in the given
> situation.
Lemme see if I am getting closer.
When reading the disk there will be head seeks necessary. When there
are two disks, each with its own complete copy of all the data, there
is no reason to keep the two disks' heads in the same place. If their
heads are in different places, a read can be issued to the disk whose
heads are closer to the desired location.
This then brings up two more questions:
1. Does the OS even know where the heads are in a modern IDE disk?
2. Is "closer" any more finely grained than a binary
positioned/not-positioned?
And I guess another question: How much does RAID 1 help and under what
kinds of usage?
Thanks,
-kb, the Kent who is getting smarter.
next prev parent reply other threads:[~2002-05-01 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 12:23 raid1 performance Jaime Medrano
2002-04-30 12:38 ` Arjan van de Ven
2002-04-30 14:21 ` Kent Borg
2002-05-01 16:35 ` Jakob Østergaard
2002-05-01 17:01 ` Kent Borg [this message]
2002-05-01 17:16 ` Justin Cormack
2002-05-01 21:23 ` Bernd Eckenfels
2002-05-02 16:37 ` Jakob Østergaard
2002-06-29 0:01 ` Bernd Eckenfels
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=20020501130127.A10936@borg.org \
--to=kentborg@borg.org \
--cc=arjanv@redhat.com \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=overflow@eurielec.etsit.upm.es \
/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