From: d tbsky <tbskyd@gmail.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: use ssd as write-journal or lvm-cache?
Date: Wed, 17 Feb 2021 16:52:59 +0800 [thread overview]
Message-ID: <CAC6SzHKj8J9nSAcvtFvAC4o1_iQCEhpY9R5305RA1nzB6bFKPA@mail.gmail.com> (raw)
In-Reply-To: <20210217110923.62fd685f@natsu>
Roman Mamedov <rm@romanrm.net>
>
> On Wed, 17 Feb 2021 11:27:58 +0800
> Why not both? It's not like you have to use the entire SSD for one or the
> other. And it's very unlikely anything will be bottlenecked by concurrent
> access to the SSD from both mechanisms.
if I use both, then data may write twice to the same ssd, it seems waste.
> Choosing one, I would prefer LVM caching, since it also gives benefit for
> reads. And the mdadm write journal feature sounds[1] more like of a
> reliability, not a performance enhancement.
at final stage data write to disk with any kind of cache. so if the
data can write to disk with optimized method,
it seems speed up the whole thing. read-cache is fine, but I don't
know how much benefit it will bring.
> In any case, in order to not add a single point of failure to the array,
> better rely not on SSD being a "datacenter" one (anything can fail), but use a
> RAID1 of two SSDs.
yes raid1 is must. "datacenter" ssd can protect the ssd-cache so it
won't suffer with power outage. so I think I can enable write-back
mode safely.
next prev parent reply other threads:[~2021-02-17 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 3:27 use ssd as write-journal or lvm-cache? d tbsky
2021-02-17 6:09 ` Roman Mamedov
2021-02-17 8:45 ` Peter Grandi
2021-02-17 10:17 ` Roman Mamedov
2021-02-17 8:52 ` d tbsky [this message]
2021-02-17 9:12 ` Peter Grandi
2021-02-17 13:50 ` d tbsky
2021-02-17 20:50 ` Peter Grandi
2021-02-17 18:03 ` antlists
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=CAC6SzHKj8J9nSAcvtFvAC4o1_iQCEhpY9R5305RA1nzB6bFKPA@mail.gmail.com \
--to=tbskyd@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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).