linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: XFS/btrfs performance after IO-less dirty throttling
Date: Fri, 16 Dec 2011 13:16:09 +0800	[thread overview]
Message-ID: <20111216051609.GA4502@localhost> (raw)
In-Reply-To: <20111216042508.GE23662@dastard>

On Fri, Dec 16, 2011 at 12:25:08PM +0800, Dave Chinner wrote:
> On Fri, Dec 16, 2011 at 09:53:11AM +0800, Wu Fengguang wrote:
> > I'm indeed happy that you don't care that much on that regression
> > introduced by me ;-)
> 
> Heh.
> 
> BTW, do these tests run to ENOSPC?

Nope. Shall ENOSPC (performance) be tested?

> >                 10829.00        +4.3%     11296.00  TOTAL xfs:xfs_delalloc_enospc
> 
> This implies that it does.

Not really. The USB key partition size is 7.1GB.
Even in the fastest 1dd case, only 4GB data is written:

wfg@bee /export/writeback% cat fat/UKEY-thresh=100M/xfs-1dd-1-3.2.0-rc3/ls-files 
131 -rw-rw-r-- 1 root root 4060078080 Dec  8 15:57 /fs/sdb3/zero-1

That's about 6.7MB/s write bandwidth running for 600 seconds.

Thanks,
Fengguang

  reply	other threads:[~2011-12-16  5:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 14:31 XFS/btrfs performance after IO-less dirty throttling Wu Fengguang
2011-12-14 14:59 ` Wu Fengguang
     [not found] ` <20111215133137.GA14562@localhost>
2011-12-16  0:31   ` Dave Chinner
2011-12-16  1:53     ` Wu Fengguang
2011-12-16  4:25       ` Dave Chinner
2011-12-16  5:16         ` Wu Fengguang [this message]
2011-12-19  1:57           ` Dave Chinner
2011-12-19  5:44             ` Wu Fengguang
     [not found]   ` <20111215135250.GB14562@localhost>
2011-12-16  5:27     ` Wu Fengguang

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=20111216051609.GA4502@localhost \
    --to=fengguang.wu@intel.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).