From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS setup advice for laptop performance ?
Date: Sat, 05 Apr 2014 00:35:08 +0200 [thread overview]
Message-ID: <7675297.F25Z3Ox7Yz@tethys> (raw)
In-Reply-To: <20140404150906.GR7442@carfax.org.uk>
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 <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next prev parent reply other threads:[~2014-04-04 22:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:02 BTRFS setup advice for laptop performance ? Swâmi Petaramesh
2014-04-04 12:33 ` Austin S Hemmelgarn
2014-04-04 12:48 ` Swâmi Petaramesh
2014-04-04 15:51 ` Austin S Hemmelgarn
2014-04-04 20:31 ` Duncan
2014-04-07 12:18 ` Johannes Hirte
2014-04-04 15:09 ` Hugo Mills
2014-04-04 22:35 ` Swâmi Petaramesh [this message]
2014-04-05 10:12 ` Duncan
2014-04-05 11:10 ` Swâmi Petaramesh
2014-04-05 12:16 ` Duncan
2014-04-05 14:13 ` Hugo Mills
2014-04-06 9:24 ` Swâmi Petaramesh
2014-04-07 15:11 ` Austin S Hemmelgarn
2014-04-08 11:56 ` Clemens Eisserer
2014-04-08 12:05 ` Austin S Hemmelgarn
2014-04-09 10:53 ` Chris Samuel
2014-04-12 13:17 ` Marc MERLIN
2014-04-12 17:12 ` Koen Kooi
2014-04-05 14:26 ` Garry T. Williams
2014-04-05 15:06 ` Duncan
2014-04-06 15:17 ` Martin Steigerwald
2014-04-09 11:08 ` Chris Samuel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7675297.F25Z3Ox7Yz@tethys \
--to=swami@petaramesh.org \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).