Am Wed, 20 Jan 2016 10:39:58 -0500 schrieb "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>: > On 2016-01-20 10:33, Al wrote: > > [very quietly] I've had autodefrag out of my mount options for a > > long while now. Is that still the recommended position? > I think it really depends on what you're doing. In my case, I > usually have it on, and the only issue I've ever seen is that Chrome > sometimes loads pages from local cache slower than it should be. I > also don't use ridiculous numbers of snapshots either (I use them > only to get a stable view of the filesystem when generating a > backup), so I don't have much experience with how they interact with > autodefrag. I'd recommend to set chrome caching to simple http cache in chrome://flags as this is more suitable for btrfs (as for most Unix file systems which deal with many small files better than with random updates in a big fat files). I experienced much improved performance and responsiveness with it. May be worth a try for you. I'd be interested in your results. chrome://flags/#enable-simple-cache-backend -- Regards, Kai Replies to list-only preferred. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
