public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Nick Piggin <npiggin@kernel.dk>
Cc: xfs@oss.sgi.com
Subject: Re: XFS performance oddity
Date: Wed, 24 Nov 2010 07:58:04 +1100	[thread overview]
Message-ID: <20101123205804.GX22876@dastard> (raw)
In-Reply-To: <20101123122449.GA4812@amd>

On Tue, Nov 23, 2010 at 11:24:49PM +1100, Nick Piggin wrote:
> Hi,
> 
> Running parallel fs_mark (0 size inodes, fsync on close) on a ramdisk
> ends up with XFS in funny patterns.
> 
> procs -----------memory---------- ---swap-- -----io---- -system--
> ----cpu----
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy
> id wa
> 24  1   6576 166396    252 393676  132  140 16900 80666 21308 104333  1 84 14  1
> 21  0   6712 433856    256 387080  100  224  9152 53487 13677 53732  0 55 45  0
>  2  0   7068 463496    248 389100    0  364  2940 17896 4485 26122  0 33 65  2
>  1  0   7068 464340    248 388928    0    0     0     0   66  207  0  0 100  0
>  0  0   7068 464340    248 388928    0    0     0     0   79  200  0  0 100  0
>  0  0   7068 464544    248 388928    0    0     0     0   65  199  0  0 100  0
>  1  0   7068 464748    248 388928    0    0     0     0   79  201  0  0 100  0
>  0  0   7068 465064    248 388928    0    0     0     0   66  202  0  0 100  0
>  0  0   7068 465312    248 388928    0    0     0     0   80  200  0  0 100  0
>  0  0   7068 465500    248 388928    0    0     0     0   65  199  0  0 100  0
>  0  0   7068 465500    248 388928    0    0     0     0   80  202  0  0 100  0
>  1  0   7068 465500    248 388928    0    0     0     0   66  203  0  0 100  0
>  0  0   7068 465500    248 388928    0    0     0     0   79  200  0  0 100  0
> 23  0   7068 460332    248 388800    0    0  1416  8896 1981 7142  0  1 99  0
>  6  0   6968 360248    248 403736   56    0 15568 95171 19438 110825  1 79 21  0
> 23  0   6904 248736    248 419704  392    0 17412 118270 20208 111396  1 82 17  0
>  9  0   6884 266116    248 435904  128    0 14956 79756 18554 118020  1 76 23  0
>  0  0   6848 219640    248 445760  212    0  9932 51572 12622 76491  0 60 40  0
> 
> Got a dump of sleeping tasks. Any ideas?

It is stuck waiting for log space to be freed up. Generally this is
caused by log IO completion not occurring or an unflushable object
preventing the tail from being moved forward.  What:

	- kernel are you running?
	- is the time resolution of the above output?
	- is the output of mkfs.xfs?
	- are your mount options?
	- is the fs_mark command line?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-11-23 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 12:24 XFS performance oddity Nick Piggin
2010-11-23 12:30 ` Nick Piggin
2010-11-23 20:58 ` Dave Chinner [this message]
2010-11-24  0:50   ` Nick Piggin
2010-11-24  3:15     ` Dave Chinner
2010-11-24  5:28       ` [PATCH] " Dave Chinner
2010-11-25  4:54         ` Nick Piggin

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=20101123205804.GX22876@dastard \
    --to=david@fromorbit.com \
    --cc=npiggin@kernel.dk \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox