Yeah, I imagine it’s not that bad in practice. I’ll probably switch eventually.

Thanks. It weirds me out when they recommend 8 GiB of memory for best performance, though. That makes sense on a server when you have huge amounts of memory, and it makes sense as a recommendation for a videogame when it’s the only process you’re running, but it’s hard to parse when it’s about a filesystem on a laptop. Makes me wonder if I’m crippling ZFS when I build a complex application or play a game? Tough to tell if you get 95% performance when 2 GiB are available or 25%.

What hardware? I’m interested in trying this on my machines, but I’m curious how much CPU it consumes and how large numbers of snapshots perform on lower-end hardware. There’s a million guides for setting up ZFS on root on the web, but finding performance evaluations specific to the root usecase is harder. All I’ve found is this from the Ubuntu on ZFS effort:

Computers that have less than 2 GiB of memory run ZFS slowly. 4 GiB of memory is recommended for normal performance in basic workloads. If you wish to use deduplication, you will need massive amounts of RAM. Enabling deduplication is a permanent change that cannot be easily reverted.

Maybe I’m misunderstanding the tech, but isn’t this irrelevant with federation? If lemmy.ml/c/privacy is squatted, then people will subscribe to (hypothetically) lemmy.privacytools.io/c/privacy.

Or are you asking with respect to just this instance and not the Lemmy defaults, since you’re administrating this one? In that case, this is a great example of the power of federation. You can pick what you think will keep the instance healthy; I don’t have an opinion.