Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Simon Kirby <sim@hostway.ca>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Hot rb_next, setup_cluster_no_bitmap
Date: Thu, 4 Aug 2011 10:28:35 -0700	[thread overview]
Message-ID: <20110804172835.GA5301@hostway.ca> (raw)
In-Reply-To: <1312466623-sup-3275@shiny>

On Thu, Aug 04, 2011 at 10:04:29AM -0400, Chris Mason wrote:

> Excerpts from Simon Kirby's message of 2011-08-03 21:32:10 -0400:
> > Perhaps as a further clue as to what is going on, on this same backup box
> > after all of the rsyncs are finished/killed and a good amount of time has
> > passed (no cleaner processes running in the background or anything),
> > "sync" is still consistently takes ~4 minutes to run, and pushes out a
> > lot to disk every time it is run. Example:
> > 
> > echo 3 > /proc/sys/vm/drop_caches
> > sync
> > echo 3 > /proc/sys/vm/drop_caches
> > sync
> > vmstat 1 &
> > time sync
> 
> Just to confirm, the profiling during this time shows your system time
> is all in rb_next?

Correct, rb_next() called from setup_cluster_no_bitmap(). Also, much of the
other CPU time is spent spinning (on refill_lock, I think).

It's in this state again now (just one overnight backup run does it). It
doesn't seem to happen for the first few hours, but shows up by the next
morning.

Simon-

      reply	other threads:[~2011-08-04 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 22:06 Hot rb_next, setup_cluster_no_bitmap Simon Kirby
2011-08-03 22:39 ` Simon Kirby
2011-08-03 23:10   ` Simon Kirby
2011-08-04  1:13     ` Chris Mason
2011-08-04  1:32     ` Simon Kirby
2011-08-04 14:04       ` Chris Mason
2011-08-04 17:28         ` Simon Kirby [this message]

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=20110804172835.GA5301@hostway.ca \
    --to=sim@hostway.ca \
    --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