From: cwillu <cwillu@cwillu.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Calvin Walton <calvin.walton@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Horrible btrfs performance due to fragmentation
Date: Sun, 31 Oct 2010 16:25:41 -0600 [thread overview]
Message-ID: <AANLkTikNywvthaU-+s5HXvh3RX=HxiFWmADW--Ln_Gga@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinWT9OyicLfdeY+AvWs=5vb5z8skZ3t6keYjk9j@mail.gmail.com>
On Sun, Oct 31, 2010 at 1:58 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Mon, Oct 11, 2010 at 6:46 PM, Calvin Walton <calvin.walton@gmail.c=
om> wrote:
>> On Mon, 2010-10-11 at 03:30 +0300, Felipe Contreras wrote:
>>> I use btrfs on most of my volumes on my laptop, and I've always fel=
t
>>> booting was very slow, but definitely sure is slow, is starting up
>>> Google Chrome:
>>>
>>> encrypted ext4: ~20s
>>> btrfs: ~2:11s
>>>
>>> I have tried different things to find out exactly what is the issue=
,
>>> but haven't quite found it yet.
>>
>> If you've been using this volume for a while, it could just have bec=
ome
>> badly fragmented. You could try btrfs's fancy online defragmentation
>> abilities to see if that'll give you an improvement:
>>
>> # btrfs filesystem defragment /mountpoint/of/volume
>>
>> Let us know if that helps, of course :)
>
> I finally managed to track down this issue. Indeed the fragmentation
> is horrible, and 'btrfs filesystem defragment' doesn't help:
>
> % cat History-old > History
> % btrfs filesystem defragment /home
> % echo 3 > /proc/sys/vm/drop_caches
>
> % time dd if=3DHistory of=3D/dev/null && time dd if=3DHistory-old of=3D=
/dev/null
> 109664+0 records in
> 109664+0 records out
> 56147968 bytes (56 MB) copied, 1.90015 s, 29.5 MB/s
> dd if=3DHistory of=3D/dev/null =A00.08s user 0.29s system 15% cpu 2.4=
58 total
> 109664+0 records in
> 109664+0 records out
> 56147968 bytes (56 MB) copied, 97.772 s, 574 kB/s
> dd if=3DHistory-old of=3D/dev/null =A00.07s user 0.80s system 0% cpu =
1:37.79 total
>
> I think this is a serious issue that *must* be fixed for 1.0. I filed
> a bug for this:
> https://bugzilla.kernel.org/show_bug.cgi?id=3D21562
btrfs fi defrag isn't recursive. "btrfs filesystem defrag /home" will
defragment the space used to store the folder, without touching the
space used to store files in that folder.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-31 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 19:58 Horrible btrfs performance due to fragmentation Felipe Contreras
2010-10-31 22:25 ` cwillu [this message]
2010-10-31 22:36 ` Felipe Contreras
2010-10-31 22:47 ` Hugo Mills
2010-11-01 15:58 ` Felipe Contreras
2010-11-01 16:09 ` Gregory Maxwell
2010-11-02 0:55 ` Chris Mason
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='AANLkTikNywvthaU-+s5HXvh3RX=HxiFWmADW--Ln_Gga@mail.gmail.com' \
--to=cwillu@cwillu.com \
--cc=calvin.walton@gmail.com \
--cc=chris.mason@oracle.com \
--cc=felipe.contreras@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).