All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <rob@robspanton.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Performance Issues
Date: Fri, 19 Sep 2014 12:45:53 -0500	[thread overview]
Message-ID: <541C6BD1.7080604@fb.com> (raw)
In-Reply-To: <1411145469.1601.2.camel@zarniwoop.blob>

On 09/19/2014 11:51 AM, Rob Spanton wrote:
> Hi,
>
> Thanks for the response everyone.
>
> I wrote:
>> I have a particularly uncomplicated setup (a desktop PC with a hard
>> disk) and I'm seeing particularly slow performance from btrfs.  A `git
>> status` in the linux source tree takes about 46 seconds after dropping
>> caches, whereas on other machines using ext4 this takes about 13s.  My
>> mail client (evolution) also seems to perform particularly poorly on
>> this setup, and my hunch is that it's spending a lot of time waiting on
>> the filesystem.
>
> The evolution problem has been improved: the sqlite db that it was using
> had over 18000 fragments, so I got evolution to recreate that file with
> nocow set.  It now takes "only" 30s to load my mail rather than 80s,
> which is better...
>
> On Fri, 2014-09-19 at 11:05 -0400, Josef Bacik wrote:
>> Weird, I get the exact opposite performance.  Anyway it's probably
>> because of your file layouts, try defragging your git dir and see if
>> that helps.  Thanks,
>
> Defragging has improved matters a bit: it now takes 26s (was 46s) to run
> git status.  Still not amazing, but at the moment I have no evidence to
> suggest that it's not something to do with the machine's hardware.  If I
> get time over the weekend I'll dig out an external hard disk and try a
> couple of benchmarks with that.
>
> For reference, these are the mount flags:
>          /dev/sda4 on / type btrfs (rw,noatime,space_cache)
>          /dev/sda4 on /home type btrfs (rw,noatime,space_cache)
>

You have an awful lot of metadata, do you have a lot of snapshots?  Also 
I'd be interested in making sure most of this is just from shitty 
metadata layout, could you make sure you have a recent version of 
trace-cmd and then drop caches and do

trace-cmd record -e sched:sched_switch git status

and send me the trace.dat so I can see where all the time is spent?  Thanks,

Josef


  reply	other threads:[~2014-09-19 17:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 12:18 Performance Issues Rob Spanton
2014-09-19 12:25 ` Swâmi Petaramesh
2014-09-19 12:58   ` Austin S Hemmelgarn
2014-09-19 12:49 ` Austin S Hemmelgarn
2014-09-19 12:59   ` Austin S Hemmelgarn
2014-09-19 13:34 ` Holger Hoffstätte
2014-09-22 11:59   ` David Sterba
2014-09-22 12:37     ` Holger Hoffstätte
2014-09-22 13:25       ` David Sterba
2014-09-19 13:51 ` Holger Hoffstätte
2014-09-19 14:53   ` Austin S Hemmelgarn
2014-09-19 16:23     ` Holger Hoffstätte
2014-09-19 17:51   ` Zach Brown
2014-09-20  8:23   ` Marc Dietrich
2014-09-20 13:41     ` Martin
2014-09-20 18:29       ` Chris Murphy
2014-09-20 14:04     ` Wang Shilong
2014-09-20 20:44       ` Marc Dietrich
2014-09-19 15:05 ` Josef Bacik
2014-09-19 16:51   ` Rob Spanton
2014-09-19 17:45     ` Josef Bacik [this message]
2014-10-30 14:23       ` Rob Spanton
2014-09-20  5:58     ` Duncan
     [not found] <CAEsGcVufqGYA3OMBUPnTBuXc0UxrrjJdFEr8kQXkLWbTcvd6Gw@mail.gmail.com>
2012-10-06 16:49 ` performance issues corn chips
2012-10-06 16:50   ` Joao Eduardo Luis
  -- strict thread matches above, loose matches on Subject: below --
2005-09-15 13:02 Performance issues tmp123
2005-09-14 19:53 Ferry van Aesch
2005-09-15 12:43 ` TheGesus
2005-09-15 12:53 ` lst_hoe01

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=541C6BD1.7080604@fb.com \
    --to=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rob@robspanton.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.