linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Performance question, RAID5
Date: Tue, 01 Feb 2011 11:37:42 +0000	[thread overview]
Message-ID: <4D47F086.9000308@anonymous.org.uk> (raw)
In-Reply-To: <AANLkTi=CdiOjA15umaaO9ORDQ9StoesC2eD5q0_e3Bb0@mail.gmail.com>

On 30/01/2011 12:12, Mathias Burén wrote:
[...]
> Ah, good point. The sda is a 60GB SSD, I should definitely move that
> to the PCI-E card, as it doesn't do heavy IO (just small random r/w).
> Then i can have 4 RAID HDDs on the onboard ctrl, and 2 on the PCI-E
> shared with the SSD. If the SSD is idle then I should get ideal
> throughputs.

Hmm, if you have an SSD, you might look at using bcache to speed up 
write access to your array. On the other hand, with only one SSD you 
potentially lose redundancy - do SSDs crash and burn like hard drives do?

If the SSD is only being used as a boot/OS drive - so near idle in 
normal use - I'd swap it for a cheap small laptop hard drive and find 
somewhere else to put the SSD to better use.

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

  parent reply	other threads:[~2011-02-01 11:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 22:48 Performance question, RAID5 Mathias Burén
2011-01-29 22:53 ` Roman Mamedov
2011-01-29 23:44   ` Mathias Burén
2011-01-29 23:57     ` Roman Mamedov
2011-01-30  0:15       ` Stan Hoeppner
2011-01-30  0:33         ` Mathias Burén
2011-01-30  0:27       ` Mathias Burén
2011-01-30  1:52     ` Keld Jørn Simonsen
2011-01-30  1:54       ` Mathias Burén
2011-01-30  5:56         ` Keld Jørn Simonsen
2011-01-30 12:12           ` Mathias Burén
2011-01-30 19:44             ` Stan Hoeppner
2011-01-30 19:46               ` Mathias Burén
2011-02-01 11:37             ` John Robinson [this message]
2011-02-01 13:53               ` Roberto Spadim
2011-02-01 14:02               ` Mathias Burén
2011-02-01 14:32                 ` Roberto Spadim
2011-01-29 23:26 ` CoolCold
2011-01-30  0:18   ` Mathias Burén
2011-01-30  4:44     ` Roman Mamedov
2011-01-30 12:09       ` Mathias Burén
2011-01-30 12:15         ` Roman Mamedov
2011-01-30 19:41           ` Mathias Burén
2011-01-30 19:54             ` Roman Mamedov
2011-01-30 19:58               ` Mathias Burén
2011-01-30 20:03             ` Stan Hoeppner
2011-01-30 21:43               ` Mathias Burén
2011-01-31  3:39                 ` Stan Hoeppner
2011-01-31  3:54                   ` Roberto Spadim
2011-01-31  8:52                 ` Keld Jørn Simonsen
2011-01-31  9:37                   ` Mathias Burén
2011-01-31 13:11                     ` Keld Jørn Simonsen
2011-01-31 14:43                       ` Roberto Spadim
2011-01-31 18:44                         ` Keld Jørn Simonsen
2011-01-31 20:42                       ` NeilBrown
2011-01-31 21:41                         ` Keld Jørn Simonsen
2011-01-31 21:43                           ` Roberto Spadim

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=4D47F086.9000308@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@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;
as well as URLs for NNTP newsgroup(s).