Le vendredi 4 avril 2014 16:09:06 Hugo Mills a écrit : > We don't have lots of reports of massive slowdowns > after a long period of use, so whatever you're doing, there seems to > be something unusual involved. > > It's almost certainly not your fault, but there would appear to be > something in your configuration or your use-case which is leading to > these problems, and without knowing what's different, it's hard to set > about identifying the problem.
I would have hard times finding what ! I have seen this on each and every machine on which I have installed BTRFS over the past 2 years. These first were Ubuntus, now there is one Mint, 2 Arch, 1 Fedora, all with decently recent kernels and "alls updates applied". All those machines do "mainly boring office tasks", email, web surf, word processing, spreadsheets. No databases except for system packages DB and KDE "akonadi" email storage... Few compilations, if any, no heavy disk tasks, all mounted with noatime, space_cache, inode_cache, etc... No torrents, no bitcoins, very seldom used Virtualbox (and this is nocow). No filesystem is over 80% full, some are below 20%... No filesystems currently have more than 4 active snapshots. All get slow like hell over time. > How are you measuring the slowdown -- do you have a > specific piece of benchmarking software, or just anecdotal evidence? When your system slowly shifts from "normally responsive" to "dreadfully slow" over time, that starting any app takes over a full minute with HD LED steady lit, that booting bhas become so long that the GUI DM dies of timeout before it even starts, and you have to restart it manualle... you can tell it's gone "sloooooow" without any benchmark figures... (Disk health good on all machines...) Go figure... -- Swâmi Petaramesh <sw...@petaramesh.org> http://petaramesh.org PGP 9076E32E -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
