The article would probably be correct. In my experience, and looking at the
archives for other posts, dedup really needs the RAM and preferably L2ARC
device as well. As someone else put it, home servers need not apply.
I would point out the very slow dataset destroy caveat depending on which
I am having a similar issue at the moment.. 3 GB RAM under ESXi, but dedup for
this zvol (1.2 T) was turned off and only 300 G was used. The pool does contain
other datasets with dedup turned on but are small enough so I'm not hitting the
memory limits (been there, tried that, never again