linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS setup advice for laptop performance ?
Date: Sat, 05 Apr 2014 13:10:13 +0200	[thread overview]
Message-ID: <12471892.pAn1KAtSS4@tethys> (raw)
In-Reply-To: <pan$ca9c0$aeb7ee6f$84e2e493$5ee834ed@cox.net>

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".

In other words, IMHO the best quality of a filesystem is to handle efficiently my 
workload - which means the FS corresponds to my needs - rather than 
necessitating that I change my workload and habits to adapt to the FS.

Looks a bit like you will have to cut one inch of your toes to fit into your 
brand new shiny shoes, ain't it ?

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.

Having a FS which advice is either to stop using what I'm using, OR to turn of 
or not use some of its key features - snapshots, COW... - which are the only 
reasons to consider using it in the 1st place... Uh.

Well... Buy a new car, let the vendor tell you you shouldn't go to the moutain 
for it isn't adapted, you shouldn't go to the sea as the engine will rust, and 
you shouldn't drive too much in cities as it will smoke too much... and not 
too much motorways either as the motor might heat a bit too much.

I need a filesystem that fits me, I don't want to have to fit my filesystem :-\


-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E


  reply	other threads:[~2014-04-05 11: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 [this message]
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=12471892.pAn1KAtSS4@tethys \
    --to=swami@petaramesh.org \
    --cc=1i5t5.duncan@cox.net \
    --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).