From: "gea@napp-it.org" <gea@napp-it.org>
To: developer@lists.illumos.org
Subject: Fast Dedup
Date: Thu, 5 Sep 2024 13:01:46 +0200 [thread overview]
Message-ID: <6b5e74cf-499e-4919-b23a-2524b5283f0f@napp-it.org> (raw)
Dedup
When realtime dedup was implemented in ZFS many years ago I thought,
wow, a real killer feature. Shortly after it was clear that it has
negative implications on RAM usage up to a catastrophic impact on RAM
performance especially in low RAM situations. In nearly all cases, the
general recomendation was then, keep it off.
In my current tests with Open-ZFS on Windows, currently 2.2.6 rc where
the new Fast Dedup feature is part of with newest commits from this
week, i came to the conclusion, that this time it can be the killer
feature as it improves performance, limits dedup table size to a value
or size if a dedup vdev and can clean up tables. Maybe in most cases it
can be enabled by default similar to the compress feature as it offers
mostly more advantages than disadvantages.
I hope this will be integrated in Illumos as the amount of advantages of
Illumos ZFS over generic Open-ZFS is limited to usability, stability and
the kernelbased SMB server as more and more newer ZFS features are not
available what affects compatibility.
Gea
--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com
reply other threads:[~2024-09-05 11:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6b5e74cf-499e-4919-b23a-2524b5283f0f@napp-it.org \
--to=gea@napp-it.org \
--cc=developer@lists.illumos.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;
as well as URLs for NNTP newsgroup(s).