All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: "Keld Jørn Simonsen" <keld@dkuug.dk>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Awful RAID5 random read performance
Date: Wed, 03 Jun 2009 00:13:05 +0100	[thread overview]
Message-ID: <4A25B201.2000705@anonymous.org.uk> (raw)
In-Reply-To: <20090602194704.GA30639@rap.rap.dk>

On 02/06/2009 20:47, Keld Jørn Simonsen wrote:
[...]
> My perception is that raid10,f2 is probably the fastest also for small random
> reads because of the lower latency, and faster transfer times due to only
> using the outer disk sectors. For writes the elevator evens out the
> ramdom access. Benchmarks may not show this effect as they are often
> done on clean file systems, where the files are allocated in the
> beginning of the fs.
> 
> For cases where you need cheap disk space, and have big files like
> .iso's then raid5 could be a good choice because it has the most space
> while maintaining fair to good performance for big files. 
> 
> In your case, using 3 disks, raid5 should give about 210 % of the nominal
> single disk speed for big file reads, and maybe 180 % for big file
> writes. raid10,f2 should give about 290 % for big file reads and 140%
> for big file writes. Random reads should be about the same for raid5 and
> raid10,f2 - raid10,f2 maybe 15 % faster, while random writes should be
> mediocre for raid5, and good for raid10,f2.

I'd be interested in reading about where you got these figures from 
and/or the rationale behind them; I'd have guessed differently...

Cheers,

John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-02 23:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 21:46 Awful RAID5 random read performance Maurice Hilarius
2009-05-31  6:25 ` Michael Tokarev
2009-05-31  7:47   ` Thomas Fjellstrom
2009-05-31 12:29     ` John Robinson
2009-05-31 15:41       ` Leslie Rhorer
2009-05-31 16:56         ` Thomas Fjellstrom
2009-05-31 18:26           ` Keld Jørn Simonsen
2009-06-02 18:54           ` Bill Davidsen
2009-06-02 19:47             ` Keld Jørn Simonsen
2009-06-02 23:13               ` John Robinson [this message]
2009-06-03 18:38                 ` Bill Davidsen
2009-06-03 19:57                   ` John Robinson
2009-06-03 22:21                     ` Goswin von Brederlow
2009-06-04 11:23                       ` Keld Jørn Simonsen
2009-06-04 22:40                       ` Nifty Fedora Mitch
2009-06-06 23:06                       ` Bill Davidsen
2009-06-01  1:19         ` Carlos Carvalho
2009-06-01  4:57           ` Leslie Rhorer
2009-06-01  5:39             ` Thomas Fjellstrom
2009-06-01 12:43               ` Maurice Hilarius
2009-06-02 14:57                 ` Wil Reichert
2009-06-02 15:14                   ` Maurice Hilarius
2009-06-02 19:47               ` Bill Davidsen
2009-06-01 11:41             ` Goswin von Brederlow
2009-06-03  1:57               ` Leslie Rhorer
2009-05-31 17:19       ` Goswin von Brederlow
2009-06-01 12:01         ` John Robinson

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=4A25B201.2000705@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=keld@dkuug.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.