From: Doug Ledford <dledford@redhat.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Mike Power <mpower@dodtsair.com>, linux-raid@vger.kernel.org
Subject: Re: RAID 1 using SSD and 2 HDD
Date: Thu, 28 Jul 2011 14:32:56 -0400 [thread overview]
Message-ID: <4E31AB58.3030206@redhat.com> (raw)
In-Reply-To: <CABYL=TppzPDszVp3cr0DnuVDAg3Hjq2dvZyP0CYEz2x3H2ZjZQ@mail.gmail.com>
On 07/19/2011 02:27 PM, Roberto Spadim wrote:
> no this not work very fast...
> use bcache or other similar ssd+harddisk cache solution (facebook
> have one solution i don´t remember the name)
> mixing ssd and hdd are a big problem, since write speed is the slowest
> (maybe ssd maybe hdd) and read speed isn´t very well since read in ssd
> can be non sequencial and at hdd sequencial is prefered, the read
> balance algorithm is tuned to use the near position device, and
> sometimes ssd isn´t used, or less used or more used...
> a bigger speed can be done using a cache solution (ssd+hdd or ssd+raid1(hdd))
> that was my test results... maybe someone have others results
You needed to use write-mostly, that would have drastically altered your
results. With write-mostly and write-behind enabled on the hard drives,
all reads go to the SSD instead of the hard drives, and writes complete
as soon as the SSD says it is done and the writes to the hard drives
happen in the background.
>
> 2011/7/19 Mike Power<mpower@dodtsair.com>:
>> Is it possible to implement a RAID 1 array using two equal size HDD and one
>> smaller and faster SSD. The idea being that the resulting RAID would have
>> the same size of the HDD while picking up the speed benefits of the SSD.
>> You can do something similar today by just buying two hybrid drives and
>> putting them in an array. By purchasing a dedicated SSD drive for that
>> purpose you gain the ability of controlling the size of the SSD portion. I
>> was hoping the RAID array could use the SSD more as a cache then a redundant
>> storage.
>>
>> Mike Power
>> --
>> 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
>>
>
>
>
--
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:[~2011-07-28 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:15 RAID 1 using SSD and 2 HDD Mike Power
2011-07-19 18:27 ` Roberto Spadim
2011-07-28 18:32 ` Doug Ledford [this message]
[not found] ` <CABYL=To6GFBwsHi_2y6Rzgvr3LbP2Z9hUN8QjYP5Wf+vJtKsXw@mail.gmail.com>
2011-07-29 13:30 ` Doug Ledford
2011-07-29 14:55 ` David Brown
2011-07-29 15:30 ` Doug Ledford
2011-07-29 15:51 ` Roberto Spadim
2011-07-19 18:32 ` Roman Mamedov
2011-07-19 19:13 ` Mike Power
2011-07-20 12:59 ` brian.foster
2011-07-28 18:31 ` Doug Ledford
2011-07-28 23:53 ` Xavier Brochard
2011-07-29 9:32 ` John Robinson
2011-07-29 13:38 ` Doug Ledford
2011-07-29 17:50 ` Xavier Brochard
2011-07-29 18:31 ` Doug Ledford
2011-07-29 16:20 ` Failures Rates Using SSD maurice
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=4E31AB58.3030206@redhat.com \
--to=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=mpower@dodtsair.com \
--cc=roberto@spadim.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.