From: Chris Mason <clm@fb.com>
To: "fengguang.wu@intel.com" <fengguang.wu@intel.com>
Cc: "jbacik@fusionio.com" <jbacik@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lkp@linux.intel.com" <lkp@linux.intel.com>
Subject: Re: 1be41b78: +18% increased btrfs write throughput
Date: Fri, 3 Jan 2014 16:07:05 +0000 [thread overview]
Message-ID: <1388765265.32640.7.camel@ret.masoncoding.com> (raw)
In-Reply-To: <20140103155421.GA7494@localhost>
On Fri, 2014-01-03 at 23:54 +0800, fengguang.wu@intel.com wrote:
> Hi Josef,
>
> FYI. We are doing 0day performance tests and happen to notice that
> btrfs write throughput increased considerably during v3.10-11 time
> frame:
>
> v3.10 v3.11 v3.12 v3.13-rc6
> --------------- ------------------------- ------------------------- -------------------------
> 50619 ~ 1% +17.0% 59209 ~ 2% +18.8% 60159 ~ 2% +20.5% 61007 ~ 0% lkp-ws02/micro/dd-write/11HDD-JBOD-cfq-btrfs-1dd
> 50619 +17.0% 59209 +18.8% 60159 +20.5% 61007 TOTAL iostat.sdd.wkB/s
>
> and it's contributed by
>
> commit 1be41b78bc688fc634bf30965d2be692c99fd11d
> Author: Josef Bacik <jbacik@fusionio.com>
> AuthorDate: Wed Jun 12 13:56:06 2013 -0400
> Commit: Josef Bacik <jbacik@fusionio.com>
> CommitDate: Mon Jul 1 08:52:28 2013 -0400
>
> Btrfs: fix transaction throttling for delayed refs
Bonus points for increasing the performance on purpose. Thanks for
running these Wu.
-chris
prev parent reply other threads:[~2014-01-03 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 15:54 1be41b78: +18% increased btrfs write throughput fengguang.wu
2014-01-03 16:07 ` Chris Mason [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=1388765265.32640.7.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=fengguang.wu@intel.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@linux.intel.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