From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: "Jan Engelhardt" <jengelh@inai.de>,
"Swâmi Petaramesh" <swami@petaramesh.org>
Subject: Re: BTRFS, getting darn slower everyday
Date: Sun, 9 Dec 2012 11:13:45 +0100 [thread overview]
Message-ID: <201212091113.45283.Martin@lichtvoll.de> (raw)
In-Reply-To: <alpine.LNX.2.01.1212090614400.31120@nerf07.vanv.qr>
Am Sonntag, 9. Dezember 2012 schrieb Jan Engelhardt:
> On Sunday 2012-10-07 16:48, Martin Steigerwald wrote:
> >>
> >> # btrfs su li /
> >> ID 256 top level 5 path UBUNTU
> >> ID 259 top level 5 path UBUNTU/@
> >> ID 261 top level 5 path UBUNTU/@tmp
> >> ID 262 top level 5 path UBUNTU/@home
> >>[...]
> >
> >This could be 100 or more subvolumes / snapshots.
> >Maybe slowness could be related to this one.
>
> Absolutely. COW snapshots cause severe fragmentation (it's
> in their nature). "Easily" reproducible by snapshotting an fs
> every day. Been there, had that.
So such a workload is only possible with pleasing speed with SSD?
I have about 5-10 snapshots on my backup 2TB eSATA disk which I currently
rsync to. This seems to work quite well still. But I have no idea how that
would turn out with 100 snapshots or more. And about 1 TB is free, so at
least I´d expect no serious freespace fragmentation like on the BTRFS in
my SSD (extra post for that one).
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-12-09 10:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 9:26 BTRFS, getting darn slower everyday Swâmi Petaramesh
2012-10-07 10:59 ` Martin Steigerwald
2012-10-07 14:05 ` Swâmi Petaramesh
2012-10-07 14:48 ` Martin Steigerwald
2012-10-08 6:16 ` Swâmi Petaramesh
2012-12-09 5:17 ` Jan Engelhardt
2012-12-09 10:13 ` Martin Steigerwald [this message]
2012-12-09 10:41 ` Roman Mamedov
2012-12-09 11:20 ` Swâmi Petaramesh
2012-12-09 11:38 ` Hugo Mills
2012-12-09 22:51 ` Bob Marley
2012-12-09 14:38 ` Jan Engelhardt
2012-10-07 11:02 ` Martin Steigerwald
2012-10-07 12:33 ` Alex
2012-10-07 13:19 ` Swâmi Petaramesh
2012-10-07 14:44 ` Martin Steigerwald
2012-10-07 22:47 ` Goffredo Baroncelli
2012-10-08 6:08 ` Swâmi Petaramesh
2012-10-08 11:38 ` Goffredo Baroncelli
2012-10-08 13:36 ` Swâmi Petaramesh
2012-10-08 15:50 ` Swâmi Petaramesh
2012-10-08 16:46 ` Goffredo Baroncelli
2012-10-08 6:22 ` Swâmi Petaramesh
2012-11-14 16:17 ` Peter Maloney
2012-10-07 13:00 ` Martin Steigerwald
2012-10-07 13:14 ` Swâmi Petaramesh
2012-10-07 14:41 ` Martin Steigerwald
2012-10-08 16:09 ` Josef Bacik
2012-10-08 16:15 ` Swâmi Petaramesh
2012-10-08 16:31 ` Josef Bacik
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=201212091113.45283.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=jengelh@inai.de \
--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).