From: Bill Davidsen <davidsen@tmr.com>
To: Janek Kozicki <janek_listy@wp.pl>
Cc: linux-raid@vger.kernel.org
Subject: Re: which raid level gives maximum overall speed? (raid-10,f2 vs. raid-0)
Date: Thu, 31 Jan 2008 10:30:25 -0500 [thread overview]
Message-ID: <47A1E991.80604@tmr.com> (raw)
In-Reply-To: <20080130192133.17b254bf@szpak>
Janek Kozicki wrote:
> Hello,
>
> Yes, I know that some levels give faster reading and slower writing, etc.
>
> I want to talk here about a typical workstation usage: compiling
> stuff (like kernel), editing openoffice docs, browsing web, reading
> email (email: I have a webdir format, and in boost mailing list
> directory I have 14000 files (posts), opening this directory takes
> circa 10 seconds in sylpheed). Moreover, opening .pdf files, more
> compiling of C++ stuff, etc...
>
>
In other words, like most systems, more reads than writes. And while
write can be (and usually are) cached and buffered, when you need the
next bit of data the program waits for it, far more user visible. If
this suggests tuning for acceptable write and max read speed, and
setting the readahead higher than default, then you have reached the
same conclusion as I did.
> I have a remote backup system configured (with rsnapshot), which does
> backups two times a day. So I'm not afraid to lose all my data due to
> disc failure. I want absolute speed.
>
> Currently I have Raid-0, because I was thinking that this one is
> fastest. But I also don't need twice the capacity. I could use Raid-1
> as well, if it was faster.
>
> Due to recent discussion about Raid-10,f2 I'm getting worried that
> Raid-0 is not the fastest solution, but instead a Raid-10,f2 is
> faster.
>
> So how really is it, which level gives maximum overall speed?
>
>
> I would like to make a benchmark, but currently, technically, I'm not
> able to. I'll be able to do it next month, and then - as a result of
> this discussion - I will switch to other level and post here
> benchmark results.
>
> How does overall performance change with the number of available drives?
>
> Perhaps Raid-0 is best for 2 drives, while Raid-10 is best for 3, 4
> and more drives?
>
>
> best regards
>
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
prev parent reply other threads:[~2008-01-31 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 18:21 which raid level gives maximum overall speed? (raid-10,f2 vs. raid-0) Janek Kozicki
2008-01-30 22:00 ` Keld Jørn Simonsen
2008-01-30 22:36 ` Janek Kozicki
2008-01-31 1:55 ` Keld Jørn Simonsen
2008-01-31 14:01 ` Janek Kozicki
2008-02-05 16:10 ` Keld Jørn Simonsen
2008-02-05 16:54 ` Justin Piszcz
2008-02-05 20:04 ` Keld Jørn Simonsen
2008-02-05 22:28 ` Justin Piszcz
2008-02-05 22:52 ` Janek Kozicki
2008-02-06 9:06 ` Peter Rabbitson
[not found] ` <47A9F96E.7050307@tmr.com>
2008-02-06 22:15 ` Janek Kozicki
2008-02-05 22:55 ` Keld Jørn Simonsen
2008-02-05 22:58 ` Justin Piszcz
2008-01-31 15:30 ` Bill Davidsen [this message]
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=47A1E991.80604@tmr.com \
--to=davidsen@tmr.com \
--cc=janek_listy@wp.pl \
--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).