From: Asdo <asdo@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Stupid question regarding RAID-1 access pattern
Date: Thu, 21 Jan 2010 09:09:32 +0100 [thread overview]
Message-ID: <4B580BBC.2040308@shiftmail.org> (raw)
In-Reply-To: <gu4hbqfzzb8.fsf@tk-cn0001.oulu.fi>
Erno Kuusela wrote:
> Robin Hill <robin@robinhill.me.uk> writes:
>
>
>> I doubt this would help much really. If you're reading sequential data
>> then it's pretty much as quick to keep reading as to seek to the next
>> chunk.
>>
>
> Only if your stripe size is smaller than your bandwidth x seek time.
> Break even stripe size for 100MB/s 10ms disks would be 1 MB, so it
> might work well with 4-10 MB stripes provided the IO stack is up to it?
>
10ms is the full stroke seek time, I suspect for smaller chunks/seeks
the time would be *much* shorter...
next prev parent reply other threads:[~2010-01-21 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 19:58 Stupid question regarding RAID-1 access pattern Curt Hartung
2010-01-06 21:37 ` Robin Hill
2010-01-06 22:13 ` Billy Crook
2010-01-06 23:10 ` Robin Hill
2010-01-21 7:34 ` Erno Kuusela
2010-01-21 8:09 ` Asdo [this message]
2010-01-07 15:17 ` Leslie Rhorer
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=4B580BBC.2040308@shiftmail.org \
--to=asdo@shiftmail.org \
--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).