From: "krautus@kr916.org" <krautus@kr916.org>
Cc: Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: hdd + ssd
Date: Sat, 24 Oct 2015 07:38:57 +0200 [thread overview]
Message-ID: <20151024073857.6a77ee5f@linux> (raw)
In-Reply-To: <CAAxjCEzE68m66mhdr7KoXG7p515cmrogyT5Yr6S18nUXK9xNnw@mail.gmail.com>
Thank you all for the suggestions!
I'll report back my progress, will take a while .. :)
Bye and have a nice week-end,
Mike
On Fri, 23 Oct 2015 23:34:00 +0200
Stefan Ring <stefanrin@gmail.com> wrote:
> On Fri, Oct 23, 2015 at 1:48 PM, Emmanuel Florac <eflorac@intellique.com> wrote:
> > YMMV, but here's my take:
> >
> > * flashcache being a facebook internal dev, probably is the most
> > largely deployed one. It's clearly production-ready.
> >
> > * EnhanceIO works fine but I haven't tested it thoroughly. It adds no
> > signature to the drives so it can be added to existing filesystems
> > (flashcache and bcache need reformatting). However that means that
> > bad thing may happen if you're careless -- it's clearly targeted at
> > always-on servers.
> >
> > * bcache works fine but the latest fixes haven't been backported, so
> > you should probably use it only with latest (4.2, 4.3) kernels. It's
> > not very mature yet but it's *friggin' fast*.
> >
> > * dm-cache is the easiest to set-up with the lvmcache command (if your
> > distro is recent enough of course). Like very very easy. It's
> > unfortunately the slowest of the pack, apparently. Doesn't need
> > reformatting IF your existing FS already lives in a LV.
>
> Very good summary, thanks! Do you also happen to know if all of these
> retain cache contents across reboots?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-10-24 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:23 hdd + ssd krautus
2015-10-22 18:27 ` Eric Sandeen
2015-10-23 11:48 ` Emmanuel Florac
2015-10-23 21:34 ` Stefan Ring
2015-10-24 5:38 ` krautus [this message]
2015-11-02 12:05 ` Emmanuel Florac
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=20151024073857.6a77ee5f@linux \
--to=krautus@kr916.org \
--cc=xfs@oss.sgi.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 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.