wohali commented on issue #611: URL: https://github.com/apache/couchdb-documentation/issues/611#issuecomment-751354340
Hm, that's more extents, but it doesn't look terrible. And 3.x will be doing more aggressive compaction than 2.x, so we're also seeing version vs. version bias here (and 2.x is end-of-life). I'm reading that just [adding `-o autodefrag` to the data mount](https://askubuntu.com/questions/84213/btrfs-defragmentation-of-files-folders) may be a better choice here. "`autodefrag` does help, performance impact is minor at best on everyday systems." But this data is also 7 years old, so I don't know how things have progressed since then. A recent [reddit post agrees](https://old.reddit.com/r/btrfs/comments/fch1v0/is_fragmentation_on_ssd_an_issue/). Or it might be acceptable to simply run [`btrfs filesystem defragment ...`](https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-filesystem) This is definitely a finer point of tuning, and while I can see that this would be useful info for CouchDB users, it's not something I'd call out as critical in the installation section. Maybe this would be better to put in the [best practices](https://github.com/apache/couchdb-documentation/tree/main/src/best-practices) under the "if it ain't broke, don't fix it" approach? I'll definitely merge a PR if it shows up, I'm just not sure we have enough data here to define this as a best practice. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
