From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS setup advice for laptop performance ?
Date: Fri, 04 Apr 2014 11:51:35 -0400 [thread overview]
Message-ID: <533ED507.3020004@gmail.com> (raw)
In-Reply-To: <1847185.lRc2jIirHz@fnix>
On 2014-04-04 08:48, Swâmi Petaramesh wrote:
> Le vendredi 4 avril 2014 08:33:10 Austin S Hemmelgarn a écrit :
>>> However I'm still concerned with chronic BTRFS dreadful performance and
>>> still find that BRTFS degrades much over time even with periodic defrag
>>> and "best practices" etc.
>>
>> I keep hearing this from people, but i personally don't see this to be
>> the case at all. I'm pretty sure the 'big' performance degradation that
>> people are seeing is due to how they are using snapshots, not a result
>> using BTRFS itself (I don't use them for anything other than ensuring a
>> stable system image for rsync and/or tar based backups).
>
> Maybe I was wrong to suppose that if a feature exists, it is supposed to be
> usable... I have used ZFS for years, and on ZFS having *hundreds* of snapshots
> of any given FS have exactly zero impact on performance...
>
> With BTRFS, some time ago I tried to use SuSE "snapper" that passes its time
> doing and releasing snapshots, but it soon made my systems unusable...
>
> Now, I only keep 2-3 manually made snapshots just for keeping a "stable and OK
> archive of my machine in a known state" just in case...
>
> But if even this has a noticeable negative impact on BTRFS performance, then
> what the hell are BTRFS snapshots good at ??
>
> Kind regards.
>
I'm not saying that using a few snapshots is a bad thing, I'm saying
that thousands of snapshots is a bad thing (I have actually seen people
with hat many, including one individual who had almost 32,000 snapshots
on the same drive). I personally do keep a few around on my system on a
regular basis, even aside from the backups, and have no noticable
performance degradation. For reference, the (main) system that I am
using has a Intel Celeron 847 running at 1.1GHz, 4G of DDR3-1333 RAM,
and a 500G 5400 RPM SATAII hard disk. My root filesystem is BTRFS
volume mounted with autodefrag,space_cache,compress-force=lzo,noatime
(the noatime improves performance (and power efficency) for btrfs
because metadata updates end up cascading up the metadata tree (updating
the atime on /etc/foo/bar causes the atime to be updated on /etc/foo,
which causes the atime to be updated on /etc, which causes the atime to
be updated on /)
next prev parent reply other threads:[~2014-04-04 15:51 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 [this message]
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
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=533ED507.3020004@gmail.com \
--to=ahferroin7@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.