From: Felipe Contreras <felipe.contreras@gmail.com>
To: Calvin Walton <calvin.walton@gmail.com>
Cc: 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 on cold cache
Date: Tue, 12 Oct 2010 00:01:35 +0300 [thread overview]
Message-ID: <AANLkTinaJU_=MuCcefOweED5g2HMpHjUra8nR6mBdoyR@mail.gmail.com> (raw)
In-Reply-To: <1286811979.9645.5.camel@ayu>
On Mon, Oct 11, 2010 at 6:46 PM, Calvin Walton <calvin.walton@gmail.com> 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 felt
>> 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 become
> 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 :)
~2:06s, so it helped a bit, but not much really, there's still
something fishy going on.
--
Felipe Contreras
prev parent reply other threads:[~2010-10-11 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 0:30 Horrible btrfs performance on cold cache Felipe Contreras
2010-10-11 15:46 ` Calvin Walton
2010-10-11 16:24 ` Chester
[not found] ` <AANLkTinQQ0Y4TcRQdRhLgeBJTcvbRyiaxxHuSeh2F0Pp@mail.gmail.com>
2010-10-11 19:16 ` Felipe Contreras
2010-10-11 21:01 ` Felipe Contreras [this message]
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='AANLkTinaJU_=MuCcefOweED5g2HMpHjUra8nR6mBdoyR@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=calvin.walton@gmail.com \
--cc=chris.mason@oracle.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).