From: David Rees <drees76@gmail.com>
To: Wil Reichert <wil.reichert@gmail.com>
Cc: linux raid <linux-raid@vger.kernel.org>
Subject: Re: SSD & mechanical disc in RAID 1
Date: Mon, 1 Feb 2010 13:10:52 -0800 [thread overview]
Message-ID: <72dbd3151002011310g57fa9b66j2798aa0acde199b2@mail.gmail.com> (raw)
In-Reply-To: <7a329d911001090953j17829cd9qca0888fbcd7b4805@mail.gmail.com>
On Sat, Jan 9, 2010 at 9:53 AM, Wil Reichert <wil.reichert@gmail.com> wrote:
> Has anyone ever tried putting an SSD and a mechanical disc in RAID 1
> using write-mostly? The goal would be to extol the speed & latency
> virtues of an SSD while retaining the integrity of the traditional
> storage. Would this setup even work as I expect it to?
I have such a setup using a 30GB OCZ Vertex and an old 120GB Seagate
7200.7 (IDE!).
Read performance is exactly as you'd expect - very fast as all reads
come from the SSD so it's as fast as the SSD (though I haven't
benchmarked it to verify). At least my seat of the pants (SOTP)
measurement in comparison to other SSDs seems very similar.
Write performance is also what you'd expect, the same as an old IDE drive.
For a budget setup, it does what I expected it to.
I suspect that if you used write-behind with a write-intent bitmap
stored only on the SSD, you'd get some of that performance back, but
potentially lose a bit of reliability.
-Dave
--
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
next prev parent reply other threads:[~2010-02-01 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 17:53 SSD & mechanical disc in RAID 1 Wil Reichert
2010-01-09 19:23 ` Keld Jørn Simonsen
2010-01-22 16:37 ` Goswin von Brederlow
2010-01-31 20:21 ` Aryeh Gregor
2010-02-01 20:56 ` Wil Reichert
2010-02-01 20:06 ` Bill Davidsen
2010-02-01 21:10 ` David Rees [this message]
2010-02-02 14:07 ` Aryeh Gregor
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=72dbd3151002011310g57fa9b66j2798aa0acde199b2@mail.gmail.com \
--to=drees76@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=wil.reichert@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).