I’m having trouble understanding all the benefits of BTRFS and how they’ll apply to me.

Copy on Write and auto-compression seem like they will free up a bit of space.

What other practical benefits will I see from using BTRFS? Are there any noticeable performance benefits?

I use my computer to dual-boot. I don’t need snapshots because I have a custom script for a fresh install. I use my PC for gaming and work. I’ve got an NVMe, two SSD’s and one HDD.

Thanks in advance!

  •  studcavity   ( @studcavity@discuss.tchncs.de ) 
    4•1 year ago

    Copy on write is likely to introduce significant performance decreases in cases where large or medium size files have a couple bytes changed. It’s usually recommended to turn CoW off on those files; I found it to be more hassle than it’s worth for a root filesystem. It is still a reasonable file system for file storage that looks more like archival - files land there and seldomly or never change. If you don’t have a specific need in mind though, I wouldn’t bother - in my opinion, it’s not great as a general purpose filesystem.

    •  Yote.zip   ( @yote_zip@pawb.social ) English
      18•1 year ago

      Copy on write is likely to introduce significant performance decreases in cases where large or medium size files have a couple bytes changed. It’s usually recommended to turn CoW off on those files

      Do you happen to have a source or benchmark for this? My understanding of CoW is that the size of the file does not matter, as BTRFS works with blocks and not files. When a block is changed, it’s written to a new location. All the old blocks that are not changed are not written again - this wouldn’t even make sense in the context of how BTRFS deduplicates blocks anyway.

      So:

      • 10 kB base file

      • modify 1kB of the content

      • == 11kB total “used” space, and 1kB of new written blocks.

      that old 1kB that is no longer part of the file will eventually be cleaned up if needed, but there’s no reason to delete it early.