this post was submitted on 14 Aug 2023
107 points (99.1% liked)

Linux

48209 readers
1519 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
107
Is it worth switching to BTRFS for the average user? (aussie.zone)
submitted 1 year ago* (last edited 1 year ago) by Zozano@aussie.zone to c/linux@lemmy.ml
40 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] yote_zip@pawb.social 23 points 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.