public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>
Subject: Re: yum upgrade on btrfs very slow
Date: Mon, 26 Oct 2009 14:35:35 +0100	[thread overview]
Message-ID: <20091026133535.GA14807@mother.pipebreaker.pl> (raw)
In-Reply-To: <20091026085545.GA5564@think>

On Mon, Oct 26, 2009 at 05:55:45PM +0900, Chris Mason wrote:
> On Wed, Oct 21, 2009 at 11:27:33AM +0200, Tomasz Torcz wrote:
> > On Thu, Oct 01, 2009 at 11:01:46AM +0200, Tomasz Torcz wrote:
> > > 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.
> > 
> >    Last update: things got noticably faster with 2.6.31.4-88.fc12.x86_64,
> > which contains backport of latest mainline btrfs (thank you, Josef!).
> > No more comlains from me (for now ;).
> 
> Fantastic. Are you running with or without barriers now?

  I stick to default settings, that means barriers I think. Overall, my
test hardware is so slow by itself, that barriers are not really noticable.
(It's 3 GHz Pentium 4 in 64 bit with single IDE 20GB drive).

-- 
Tomasz Torcz               RIP is irrevelant. Spoofing is futile.
xmpp: zdzichubg@chrome.pl     Your routes will be aggreggated. -- Alex Yuriev


  reply	other threads:[~2009-10-26 13:35 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
2009-10-21  9:27           ` Tomasz Torcz
2009-10-26  8:55             ` Chris Mason
2009-10-26 13:35               ` Tomasz Torcz [this message]
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=20091026133535.GA14807@mother.pipebreaker.pl \
    --to=tomek@pipebreaker.pl \
    --cc=chris.mason@oracle.com \
    --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