linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich@noir.com>
To: linux-btrfs@vger.kernel.org
Subject: Confused by performance
Date: Mon, 24 May 2010 14:08:13 -0700	[thread overview]
Message-ID: <4BFAEABD.2070700@noir.com> (raw)

I've just started to work with btrfs so I started with a benchmark.  On 
four identical servers, (2 dual core cpus, single local disk), I built 
filesystems - ext3, ext4, nilfs2, and btrfs.  I checked out a sizable 
code tree and timed a build.  The build is parallelized to use 4 threads 
when possible.

I'm seeing similar build times on ext[34] and nilfs2 but I'm seeing 
almost double the times for btrfs using default options.  And I'm having 
trouble reconciling this performance cost with the benchmarks I'm seeing 
around the net.

Is this a common result?  Is there a trick to getting ext4 competitive 
performance out of btrfs?  Is my application a poor choice for btrfs?  
Am I missing something obvious here?

--rich



             reply	other threads:[~2010-05-24 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 21:08 K. Richard Pixley [this message]
2010-05-25  3:59 ` Confused by performance Mike Fedyk
2010-05-28  1:45 ` K. Richard Pixley
2010-06-16 18:08   ` K. Richard Pixley
2010-06-16 19:21     ` Roberto Ragusa
     [not found]       ` <AANLkTinM6ab_KEynfgvVT9v5TmcogoLZ0PLAz2oPnsiS@mail.gmail.com>
2010-06-16 19:35         ` Freddie Cash
2010-06-16 19:56           ` Roberto Ragusa
2010-06-17  6:57           ` David Brown
2010-06-16 21:44     ` Daniel J Blueman
2010-06-17  9:57     ` 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=4BFAEABD.2070700@noir.com \
    --to=rich@noir.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;
as well as URLs for NNTP newsgroup(s).