Vain lisko.

  • 24 Posts
  • 247 Comments
Joined 4M ago
cake
Cake day: Aug 09, 2022

help-circle
rss

I wonder how the bright people over at lemmy.ml and lemmygrad are attempting to explain this. Probably what hfkldjbuq wrote (“funded and led by the CIA”).



Yeah I definitely get that. What I wanted to say was just something along the lines of, “statehood equals terror”, so by all means…


While I don’t disagree, all states pretty much engage in terror.



CaspianReports is not as good as it used to be, I think. I stopped watching it a long time ago.








And then when Lemmy adopts the AT protocol it will become the world’s biggest social site






Religion is already an identity, so you can’t turn it into one…


Admittedly I don’t really know what I’m doing, but I came at a set of options after reading articles online and looking at the documentation. I ended up with this set of options:

noatime,nodatacow,autodefrag

noatime and nodatacow should obviously increase speed because it’s just doing less. I have not yet determined if autodefrag is worth it, but in theory it helps the mechanical disk in the long run by having it seek less. You lose some performance I think especially when a lot of data is being written, but my expectation is that it does more good than harm.

I tried alternative approaches like disabling autodefrag and enabling datacow but with compression to see if compression would significantlly boost performance (by taking some load off of the disk and putting it onto the CPU/RAM, which are faster on my system), but that didn’t help at all and I just went back to nodatacow.

I guess the smartest thing would be to just replace the disk with a fast SSD and this problem would probably just go away, but even today computers are still shipping with very slow hard drives, which doesn’t agree with Linux anymore.

Note: Also even before btrfs when I was running ext4 I still had to tweak it like disable atime and turn off journaling. For my use case the best FS is probably FreeBSD’s file system, which doesn’t need journaling or cow, but can just do soft updates which keeps the FS healthy and doesn’t cost anything. A power failure could only result in unwritten data but never file system corruption.


I find that the pros outweigh the cons. I had to disable datacow and a couple things but overall I got more or less the same performance in the end plus some nice features like pooling storage.



btrfs performed very poorly on my slow spinning drive 🦥 so I had to disable most of its features. A tool like this might still be useful for me