linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Spanton <rob@robspanton.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Performance Issues
Date: Thu, 30 Oct 2014 14:23:24 +0000	[thread overview]
Message-ID: <1414679004.7867.39.camel@zarniwoop.blob> (raw)
In-Reply-To: <541C6BD1.7080604@fb.com>

[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]

Hi 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.

So I recently upgraded my desktop (now an i7-5820K on a Gigabyte
GA-X99-UD4 motherboard with 32GB of RAM), and moved the disk with this
problematic filesystem across to it.  With this new setup, I still get
reasonably poor performance: the git status now takes ~26 seconds after
dropping caches.  (Although note that this git repo has had been
repacked since I did the above benchmarks.)

I have also had the disk out on a USB-to-SATA adapter plugged into my
laptop, and seen similarly poor results.

So I've put the output of this command:

        trace-cmd record -T -e sched:sched_switch -o /tmp/trace.dat git status

Here: http://robspanton.com/2014/10/trace.dat.xz

If anyone has any further ideas about how to remedy this situation,
please do let me know!

Cheers,

Rob

(Not subscribed to this list, so please CC me.)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-30 14:23 UTC|newest]

Thread overview: 23+ 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
2014-10-30 14:23       ` Rob Spanton [this message]
2014-09-20  5:58     ` Duncan

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=1414679004.7867.39.camel@zarniwoop.blob \
    --to=rob@robspanton.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).