All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: John Wyzer <john.wyzer@gmx.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: abysmal performance
Date: Fri, 29 Apr 2011 11:01:54 -0400	[thread overview]
Message-ID: <1304089239-sup-5110@think> (raw)
In-Reply-To: <1304088305-sup-3784@localhost>

Excerpts from John Wyzer's message of 2011-04-29 10:46:08 -0400:
> Currently on 
> commit 7cf96da3ec7ca225acf4f284b0e904a1f5f98821
> Author: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
> Date:   Mon Apr 25 19:43:53 2011 -0400
>     Btrfs: cleanup error handling in inode.c
> 
> merged into 2.6.38.4
> 
> I'm on a btrfs filesystem that has been used for some time. Let's say nine 
> months. Very recently I noticed performance getting worse and worse.
> Most of the time it feels as if the system is just busy with iowait.
> Write and read performance during random access is mostly around 2MB/s,
> sometimes 1MB/s or slower. It's better for big files which can be read with about
> 6-9MB/s. The disk is a reasonably recent SATA disk (WDC_WD3200BEVT) so 30MB/s
> or 40MB/s linear reading should not be a problem.
> 
> rootfs                291G  242G   35G  88% /
> 
> I tried  btrfs filesystem defragment -v / but did not notice any improvement 
> after that.
> 
> Is this a known phenomenon? :-)
> 

Sounds like you're hitting fragmentation, which we can confirm with
latencytop.  Please run latencytop while you're seeing poor performance
and take a look at where you're spending most of your time.

-chris

  reply	other threads:[~2011-04-29 15:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 14:46 abysmal performance John Wyzer
2011-04-29 15:01 ` Chris Mason [this message]
2011-04-30 17:33   ` Mitch Harder
2011-04-30 20:40     ` John Wyzer
2011-04-30 22:16       ` Mitch Harder
2011-04-30 22:33         ` John Wyzer
2011-05-03 11:05           ` Chris Mason
2011-05-03 11:06           ` Chris Mason
2011-04-30 23:55     ` Peter Stuge
2011-05-03 10:33       ` Bernhard Schmidt
2011-05-03 11:00         ` cwillu
2011-05-03 11:26           ` Bernhard Schmidt
2011-05-03 11:08         ` Chris Mason
2011-05-03 11:30           ` Bernhard Schmidt
2011-05-03 11:36             ` Chris Mason
2011-05-03 11:43               ` Bernhard Schmidt
2011-05-03 12:52                 ` Chris Mason
2011-05-03 13:03                   ` Bernhard Schmidt
2011-05-03 13:41                     ` Mitch Harder
2011-05-03 14:41                   ` Daniel J Blueman
2011-05-03 15:42                     ` Mitch Harder
2011-05-03 16:51                       ` Chris Mason
2011-05-03 14:54             ` Daniel J Blueman
2011-05-03 15:10               ` Bernhard Schmidt
     [not found]   ` <1304100271-sup-4177@localhost>
     [not found]     ` <1304100862-sup-1493@think>
     [not found]       ` <1304107977-sup-3815@localhost>
     [not found]         ` <1304110058-sup-7292@think>
     [not found]           ` <1304146193-sup-2200@localhost>
2011-04-30 20:51             ` John Wyzer
  -- strict thread matches above, loose matches on Subject: below --
2011-06-20 21:51 Abysmal Performance Henning Rohlfs
2011-06-21  0:12 ` Josef Bacik
2011-06-21  7:10   ` Henning Rohlfs
2011-06-21  8:00 ` Sander
2011-06-21  9:26   ` Henning Rohlfs
2011-06-21 15:18     ` Josef Bacik
2011-06-21 16:55       ` Henning Rohlfs
2011-06-21 15:24 ` Calvin Walton
2011-06-22 14:15   ` Henning Rohlfs
2011-06-22 15:39     ` Josef Bacik
2011-06-22 15:57       ` Calvin Walton
2011-06-22 15:58         ` Josef Bacik

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=1304089239-sup-5110@think \
    --to=chris.mason@oracle.com \
    --cc=john.wyzer@gmx.de \
    --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 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.