From: Massimo Maggi <massimo@mmmm.it>
To: linux-btrfs@vger.kernel.org
Subject: New idea about RAID and SSD
Date: Tue, 01 Sep 2009 14:44:54 +0200 [thread overview]
Message-ID: <4A9D1746.1020407@mmmm.it> (raw)
Hi,
SSDs have low latency but a high price per GB,
Traditional hard disks have high latency, but high sequential read/write
speed and low price per GB.
Is possibile to use a SSD for metadata, which requires many seeks and is
relatively small, in a special "RAID mode" with a traditional hard disk
for the extents of the real data?
A cheap but performant SSD (maybe 32 GB) + a big and fast HD (maybe 1.5
TB, or two in RAID0 - 3TB ), wouldn't create an array much cheaper than
a ssd-only array of the same size, and much faster (in
not-only-sequential workload) than one or two traditional HDs in RAID0?
Would it work?
Thank you for your precious time!
Massimo Maggi
massimo@mmmm.it
next reply other threads:[~2009-09-01 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 12:44 Massimo Maggi [this message]
2009-09-01 13:05 ` New idea about RAID and SSD Sander
2009-09-01 13:10 ` jim owens
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=4A9D1746.1020407@mmmm.it \
--to=massimo@mmmm.it \
--cc=linux-btrfs@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