4 ms·
I thought the problem was that it required an epic amount of system RAM to be efficient? It seemed a bit counterproductive to me to try to save some cheap disk
by jandrese 11y ago
I thought the problem was that it required an epic amount of system RAM to be efficient? It seemed a bit counterproductive to me to try to save some cheap disk space by buying hundreds of dollars of RAM.
- Dylan16807 11y agoI gave it much more than the already-high recommended amount of RAM. At one point I tested something like 6GB of RAM for 100GB of data. As far as I know dedup scatters small data chunks by hash across the disk. Absolutely awful performance when your seek times are non-zero. I was looking at speeds in the single digit megabytes per second. Compared to saturating things just fine with dedup off. I gave it a chunk of SSD for L2ARC and that didn't help either, and it never wrote more than a few hundred megabytes of data to it. Currently I'm doing out-of-band deduplication on btrfs and it works great. Dedup uses the same copy on write as snapshots do, and causes zero problems.
- cm3 11y agoFWIW, DragonflyBSD HAMMER1's dedup runs well on small machines (2GB) without hiccups.