From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>, Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS setup advice for laptop performance ?
Date: Mon, 07 Apr 2014 11:11:11 -0400 [thread overview]
Message-ID: <5342C00F.8070001@gmail.com> (raw)
In-Reply-To: <12471892.pAn1KAtSS4@tethys>
On 2014-04-05 07:10, Swâmi Petaramesh wrote:
> Le samedi 5 avril 2014 10:12:17 Duncan wrote [excellent performance advice
> about disabling Akonadi in BTRFS etc]:
>
> Thanks Duncan for all this excellent discussion.
>
> However I'm still rather puzzled with a filesystem for which advice is "if you
> want tolerable performance, you have to turn off features that are the default
> with any other FS out there (relatime -> noatime) or you have to quit using
> this database, or you have to fiddle around with esoteric option such as
> disabling COW wich BTW is one of BTRFS most promiment features".
>
The only reason AFAIK that noatime isn't the default on other
filesystems is because it breaks stuff like mutt. Other than that,
nobody really uses atimes, and noatime will in-fact get you better
performance on any filesystem.
> [...]
> To put it plain flat clear, even if "relatime" causes writes, every other FS
> out there can cope with it. Even if akonadi is heavy and a disk resource hog,
> any other FS out there can cope with it and still maintain acceptable, usable
> performance.
>
This is because every other filesystem (except ZFS) doesn't use COW
semantics. IIRC, using those same features on ZFS causes the same
problems. This in fact brings to mind one of the biggest reasons that I
refuse to use KDE (or systemd for that matter), KDE systems run slower
in my experience even on ext4, XFS, and JFS, not just on COW filesystems.
next prev parent reply other threads:[~2014-04-07 15:11 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
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 [this message]
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=5342C00F.8070001@gmail.com \
--to=ahferroin7@gmail.com \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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).