mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "Timothy Normand Miller" <theosib@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HELP: Getting unexpected fakeraid behavior. Fix?
Date: Sun, 6 Jul 2008 13:19:37 -0700	[thread overview]
Message-ID: <20080706131937.13065312@infradead.org> (raw)
In-Reply-To: <9871ee5f0807061307ncc55104y477c57be3e91b75f@mail.gmail.com>

On Sun, 6 Jul 2008 16:07:14 -0400
"Timothy Normand Miller" <theosib@gmail.com> wrote:

Him

> - So since fakeraid, as far as Linux is concerned, is just software
> RAID, behavior and performance of fakeraid (dm) and software RAID (md)
> should be identical (via the same drive controller).

there's a few minor nits on this concerning disk layout for non-RAID1;
for RAID1 they should be equivalent.

> 
> Since RAID1 is a mirrored configuration, it's possible to distribute
> reads across the drives, improving throughput and latency over a
> single drive on random reads.

This is.. borderline true. Let me explain the caveats;
for a SINGLE THREADED workload, there is actually no difference. 
Balancing long sequential reads over the 2 disks isn't such a good idea
for that case, since it just introduces seeks rather than keep up with
the streaming speed.
Balancing seeks; there might be some theoretical advantage because you
could, again in theory, do shorter seeks if you keep one head at the
inside and one the other disk head on the outside. In practice... a lot
of the seek time is rotational latency so it's not as big a deal as it
may sound; the moment you seek you pay a ton.


> 
> I have written a program that, on start up, reads through thousands of
> small files, and as a result does a great deal of random reads for
> several minutes.  While that was going on, I ran "iostat -d 2".  My
> observation was that any writes that occurred were correctly sent to
> both disks, but all reads were being requested ONLY from the first
> drive.

if your application is single threaded this isn't totally unexpected as
a result...



-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-06 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06 20:07 Timothy Normand Miller
2008-07-06 20:19 ` Arjan van de Ven [this message]
2008-07-06 20:44   ` Timothy Normand Miller
2008-07-06 21:24   ` Timothy Normand Miller
2008-07-07  1:22     ` Timothy Normand Miller
2008-07-07  1:26       ` Timothy Normand Miller
2008-07-07  9:57         ` Joseph Fannin
2008-07-07 11:31           ` Timothy Normand Miller

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=20080706131937.13065312@infradead.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=theosib@gmail.com \
    /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

all inboxes | Powered by JetHome®