linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: Thomas Fjellstrom <thomas@fjellstrom.ca>, linux-raid@vger.kernel.org
Subject: Re: Best option for SSD caching on a md raid array?
Date: Mon, 08 Feb 2016 09:36:32 +0100	[thread overview]
Message-ID: <56B85390.9050505@hesbynett.no> (raw)
In-Reply-To: <1670804.QnHtKWfib8@nell>

Hi,

If the server is going to have reasonably long uptimes, then lots of ram
could easily be a better choice than an SSD caching system.  I don't
know how you are planning your "dual raid5 array", nor what sort of VM's
you are dealing with.  But the key point of an SSD cache is to get fast
access to common data with random access patterns, since a raid array
will give you plenty of bandwidth for large serial accesses.  And while
an SSD is fast for random reads, having the data in the server's cache
is even faster.


On 08/02/16 06:14, Thomas Fjellstrom wrote:
> Hi,
> 
> I'm planning on setting up a dual raid5 array for hosting vm's off LVM, I would 
> like to add an ssd cache to help with typical server system loads, and some 
> mixed read/write loads for game servers.
> 
> I'm wondering what the "best" route for me to go is. There's a few options 
> that I know of, like flashcache, dm-cache, and bcache. The question is which of 
> those is better suited to my use case?
> 
> Also wondering which ones people here use, and what they use it for.
> 
> Thanks!
> 


  reply	other threads:[~2016-02-08  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08  5:14 Best option for SSD caching on a md raid array? Thomas Fjellstrom
2016-02-08  8:36 ` David Brown [this message]
2016-02-08 15:45   ` Jens-U. Mozdzen
2016-02-08 20:21   ` Thomas Fjellstrom
2016-02-08  9:38 ` Mateusz Korniak
2016-02-08 15:34 ` John Stoffel
2016-02-10 22:13   ` Pasi Kärkkäinen
2016-02-10 22:21     ` John Stoffel
2016-02-10 22:54       ` Pasi Kärkkäinen

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=56B85390.9050505@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomas@fjellstrom.ca \
    /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).