From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: "Swâmi Petaramesh" <swami@petaramesh.org>
Subject: Re: BTRFS, getting darn slower everyday
Date: Sun, 7 Oct 2012 16:41:59 +0200 [thread overview]
Message-ID: <201210071641.59272.Martin@lichtvoll.de> (raw)
In-Reply-To: <5071801B.4090704@petaramesh.org>
Am Sonntag, 7. Oktober 2012 schrieb Swâmi Petaramesh:
> Le 07/10/2012 15:00, Martin Steigerwald a écrit :
> > I forgot to mention mount options? Which one do you use?
>
> root@tethys:/etc# grep btrfs fstab
> /dev/VG1/BTR_POOL / btrfs
> subvol=UBUNTU/@,space_cache,autodefrag,compress=lzo,relatime 0 0
> /dev/sda2 /boot btrfs
> subvol=UBUNTU/@boot,space_cache,autodefrag,relatime 0 0
> /dev/VG1/BTR_POOL /tmp btrfs
> subvol=UBUNTU/@tmp,space_cache,autodefrag,compress=lzo,relatime
> 0 0 /dev/VG1/BTR_POOL /home btrfs
> subvol=UBUNTU/@home,space_cache,autodefrag,compress=lzo,relatime 0 0
> /dev/VG1/BTR_POOL /storage btrfs
> subvol=STORAGE,space_cache,autodefrag,compress=lzo,relatime 0 0
> /dev/VG1/BTR_POOL /data/BIG btrfs
> subvol=DATA/BIG,space_cache,compress=lzo,noatime 0 0
> /dev/VG1/BTR_POOL /data/VBOX_HIDDEN btrfs
> subvol=DATA/VBOX_HIDDEN,space_cache,compress=lzo,noatime 0 0
> /dev/VG1/BTR_POOL /data/VBOX_VMS btrfs
> subvol=DATA/VBOX_VMS,space_cache,compress=lzo,noatime 0 0
Hmmm, is the slowness on all of these?
For the VBOX volumes I would have a possible explaination for slowness.
Unless the subvolume is mounted with nodatacow, which it isn´t according
to above output, every write to the VM image goes to a new location. Thus
this increases fragmentation. While autodefrag might mitigate some of
these, it may not be enough. AFAIK its only efficient for certain use cases.
So or so it does not appear tha tthe VBOX volumes use autodefrag.
Could you try filefrag -v on some of the bigger VM image files?
I also wonder about the absence of inode_cache, but this could either be
default by now or BTRFS remembers whether what has initially been set. But
you could try this one. Especially on the filesystems with lots of inodes.
Thanks,
--
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-10-07 14:42 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
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 [this message]
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=201210071641.59272.Martin@lichtvoll.de \
--to=martin@lichtvoll.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).