From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs und lvm-cache?
Date: Wed, 23 Dec 2015 21:38:09 +0100 [thread overview]
Message-ID: <567B0631.2080801@googlemail.com> (raw)
In-Reply-To: <567AFF04.1030200@gmx.de>
On 12/23/15 21:07, Neuer User wrote:
> Understood. However, do SSDs really do automatic deduplication? I might
> be completely wrong here, but that sounds to be a rather complex
> mechanism, requiring lots of RAM to deduplicate 100 GB. I wouldn't have
> thought that typical SSDs include that?
tl;dr: no, because delta encoding/write buffer coalescing is not dedupe.
This is one of those persistent myth that has been kept alive by the
internet rumor machine. It has its roots in a series of blog articles [1]
and turned out to be panic coupled with FUD and fueled by a lack of factual
information.
I suggest everyone read the article(s), ALL the comments and then get back
to drinking. :o)
In SSD arrays dedupe is generally seen as a good thing.
-h
[1] http://storagemojo.com/2011/06/27/de-dup-too-much-of-good-thing/
next prev parent reply other threads:[~2015-12-23 20:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:45 btrfs und lvm-cache? Neuer User
2015-12-23 11:21 ` Martin Steigerwald
2015-12-23 11:38 ` Neuer User
2015-12-23 19:45 ` Noah Massey
2015-12-23 20:07 ` Neuer User
2015-12-23 20:38 ` Holger Hoffstätte [this message]
2015-12-23 19:49 ` Chris Murphy
2015-12-23 20:21 ` Neuer User
2015-12-23 20:56 ` Chris Murphy
2015-12-24 15:19 ` Neuer User
2015-12-23 20:24 ` Neuer User
2015-12-23 20:59 ` Chris Murphy
2015-12-24 2:04 ` Duncan
2015-12-24 15:24 ` Neuer User
2015-12-24 14:56 ` Piotr Pawłow
2015-12-24 15:29 ` Neuer User
2015-12-24 16:42 ` Piotr Pawłow
2015-12-25 17:11 ` Neuer User
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=567B0631.2080801@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--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