BTRFS and ZFS support real deduplication via copy on write, and would eliminate all current disadvantages of symlink and hardlink deduplication. It just works.
yeah that’s a good point, I’ll add an option to take advantage of this if you know you’re running on a filesystem where that works as intended.
Why have it be one huge python source file?
oh don’t worry, it’s all separate files during development – there’s a build-stage which bundles everything up into a single file for distribution. But thanks for the concern :D
suzune@ani.social 8 months ago
Just a remark from someone who runs ZFS since the beginning. Many people don’t like the deduplication feature because of its memory footprint.
It’s also nice to have this feature without relying on a certain filesystem.
chellomere@lemmy.world 8 months ago
I assume you mean automatic deduplication? I haven’t used ZFS, but BTRFS does not have that. There are a variety of ways to perform deduplication, I have duperemove scheduled to run regularly.
If ZFS is still capable of being instructed to perform deduplication when automatic deduplication is turned off, which it really should be able to do, then this should work even with it turned off.