From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: Carlos Mennens <carloswill@gmail.com>,
Mdadm <linux-raid@vger.kernel.org>
Subject: Re: RAID Configuration For New Home Server
Date: Sat, 5 Jun 2010 17:45:29 +0000 [thread overview]
Message-ID: <AANLkTim1GIDahyG_Sx37SL0rmPa3J3W7nNfYEiMzsyu3@mail.gmail.com> (raw)
In-Reply-To: <4C06794F.8030908@anonymous.org.uk>
On Wed, Jun 2, 2010 at 3:31 PM, John Robinson
<john.robinson@anonymous.org.uk> wrote:
>
> I'd consider a larger than default chunk size for the RAID-5.
+1 absolutely
When building a server for storing mostly video files on RAID-6, the
files being around 500MB to 4GB in size, I ended up with 256KB chunks.
Gained quite a bit of speed compared to the default! (Also remember to
play around with stripe cache after you're up and running.)
(I did some very basic benchmarking. I repeated some tests I found
online, which indicated that RAID chunks around 256KB were fastest. My
tests agreed.)
I would consider not building a swap partition at all, but rather use
a swap *file*, that you can put on any partition. Here's a howto:
http://www.linux.com/archive/feature/113956 Alternately consider
putting the swap file on a RAID0 for the most speed, which also costs
you a smaller chunk of each disk for the same swap size. The safest
swap is mirrored though, and I'd agree with RAID10,f2 in that case.
Hmm ... no conclusion ... I'm thinking out loud more than I intended
to. To state something concrete: I think my conclusion du jour
regarding swap RAID is probably that swap space isn't that important
anyway for regular use - one should always have enough memory to begin
with so relegating swap mostly to emergency use. Regarding swap as an
emergency feature, it's probably best to have it mirrored - you
wouldn't want your swap space to ever vanish in the middle of
anything. And so I'd go with RAID10,f2, which is by far the fastest
mirror.
-- Kristleifur
next prev parent reply other threads:[~2010-06-05 17:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 17:08 RAID Configuration For New Home Server Carlos Mennens
2010-06-01 17:56 ` Mark Knecht
2010-06-01 22:59 ` Ryan Wagoner
2010-06-02 4:03 ` Leslie Rhorer
2010-06-02 6:08 ` Simon Matthews
2010-06-02 6:33 ` Leslie Rhorer
2010-06-02 7:51 ` tron
2010-06-02 14:24 ` Leslie Rhorer
2010-06-02 7:54 ` tron
2010-06-02 13:00 ` Carlos Mennens
2010-06-02 15:31 ` John Robinson
2010-06-05 17:45 ` Kristleifur Daðason [this message]
2010-06-05 17:19 ` Leslie Rhorer
2010-06-05 19:41 ` Mark Knecht
2010-06-05 23:56 ` Leslie Rhorer
2010-06-06 1:04 ` Keld Simonsen
2010-06-06 1:57 ` Simon Matthews
2010-06-06 2:01 ` Leslie Rhorer
2010-06-06 2:43 ` Mark Knecht
2010-06-06 5:19 ` Leslie Rhorer
2010-06-06 11:23 ` Leslie Rhorer
2010-06-06 14:56 ` Mark Knecht
2010-06-06 20:47 ` Leslie Rhorer
2010-06-06 14:50 ` Mark Knecht
2010-06-06 20:35 ` 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=AANLkTim1GIDahyG_Sx37SL0rmPa3J3W7nNfYEiMzsyu3@mail.gmail.com \
--to=kristleifur@gmail.com \
--cc=carloswill@gmail.com \
--cc=john.robinson@anonymous.org.uk \
--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).