From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: yum upgrade on btrfs very slow
Date: Thu, 1 Oct 2009 11:01:46 +0200 [thread overview]
Message-ID: <20091001090146.GA14522@mother.pipebreaker.pl> (raw)
In-Reply-To: <20090930194350.GA29166@mother.pipebreaker.pl>
On Wed, Sep 30, 2009 at 09:43:51PM +0200, Tomasz Torcz wrote:
> >
> > If you're comparing w/ext3 and wondering why btrfs is sooooooo much
> > slower it might be because btrfs has barriers on by default and ext3
> > doesn't. You could mount -o nobarrier for btrfs or mount -o barrier=1
> > for ext3 for a proper comparison.
> >
> > (Assuming your dmesg doesn't have messages from btrfs about disabling
> > barriers).
>
> I wouldn't expect barriers to work here (reminder, this is PATA drive
> on ICH7 sata controller), but I will test tomorrow with nobarrier.
> Then I probably check his "yum upgrade" under seekwatcher on friday.
Nobarrier result are here:
http://pipebreaker.pl/dump/sysrq_w-nobarrier.txt.bz2
http://pipebreaker.pl/dump/vmstat-nobarrier.txt.bz2
My observation: still slow. Just a note on my unscientific methodology:
I've got two very similar machines with Rawhide, one on ext4, second
on btrfs. Every day I do "yum upgrade" on both. Ext4 one finishes much
faster thatn btrfs. This is especially visible while yum is in "cleanup phase".
On ext4 most packages are cleaned'up in under one second time. On btrfs
this takes few seconds.
Whole transaction ends in couple of minutes on ext4. On btrfs it takes 5x
longer.
--
Tomasz Torcz RIP is irrevelant. Spoofing is futile.
xmpp: zdzichubg@chrome.pl Your routes will be aggreggated. -- Alex Yuriev
next prev parent reply other threads:[~2009-10-01 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 12:18 yum upgrade on btrfs very slow Tomasz Torcz
2009-09-28 13:35 ` Chris Mason
2009-09-29 6:18 ` Tomasz Torcz
2009-09-29 13:25 ` Chris Mason
2009-09-30 19:43 ` Tomasz Torcz
2009-10-01 9:01 ` Tomasz Torcz [this message]
2009-10-21 9:27 ` Tomasz Torcz
2009-10-26 8:55 ` Chris Mason
2009-10-26 13:35 ` Tomasz Torcz
2009-10-01 9:04 ` Jens Axboe
2009-10-05 12:09 ` Ric Wheeler
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=20091001090146.GA14522@mother.pipebreaker.pl \
--to=tomek@pipebreaker.pl \
--cc=linux-btrfs@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