mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Josef Bacik <josef@toxicpanda.com>,
	kernel test robot <rong.a.chen@intel.com>,
	David Sterba <dsterba@suse.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"lkp@01.org" <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
	Qu Wenruo <wqu@suse.com>
Subject: Re: [LKP] [btrfs]  302167c50b:  fio.write_bw_MBps -12.4% regression
Date: Fri, 24 May 2019 10:36:00 -0400	[thread overview]
Message-ID: <20190524143558.mem7gircjjmut54f@MacBook-Pro-91.local> (raw)
In-Reply-To: <874l5k9tx2.fsf@yhuang-dev.intel.com>

On Fri, May 24, 2019 at 03:46:17PM +0800, Huang, Ying wrote:
> "Huang, Ying" <ying.huang@intel.com> writes:
> 
> > "Huang, Ying" <ying.huang@intel.com> writes:
> >
> >> Hi, Josef,
> >>
> >> kernel test robot <rong.a.chen@intel.com> writes:
> >>
> >>> Greeting,
> >>>
> >>> FYI, we noticed a -12.4% regression of fio.write_bw_MBps due to commit:
> >>>
> >>>
> >>> commit: 302167c50b32e7fccc98994a91d40ddbbab04e52 ("btrfs: don't end
> >>> the transaction for delayed refs in throttle")
> >>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git pending-fixes
> >>>
> >>> in testcase: fio-basic
> >>> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 64G memory
> >>> with following parameters:
> >>>
> >>> 	runtime: 300s
> >>> 	nr_task: 8t
> >>> 	disk: 1SSD
> >>> 	fs: btrfs
> >>> 	rw: randwrite
> >>> 	bs: 4k
> >>> 	ioengine: sync
> >>> 	test_size: 400g
> >>> 	cpufreq_governor: performance
> >>> 	ucode: 0xb00002e
> >>>
> >>> test-description: Fio is a tool that will spawn a number of threads
> >>> or processes doing a particular type of I/O action as specified by
> >>> the user.
> >>> test-url: https://github.com/axboe/fio
> >>>
> >>>
> >>
> >> Do you have time to take a look at this regression?
> >
> > Ping
> 
> Ping again.
> 

This happens because now we rely more on on-demand flushing than the catchup
flushing that happened before.  This is just one case where it's slightly worse,
overall this change provides better latencies, and even in this result it
provided better completion latencies because we're not randomly flushing at the
end of a transaction.  It does appear to be costing writes in that they will
spend more time flushing than before, so you get slightly lower throughput on
pure small write workloads.  I can't actually see the slowdown locally.

This patch is here to stay, it just shows we need to continue to refine the
flushing code to be less spikey/painful.  Thanks,

Josef

  reply	other threads:[~2019-05-24 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03  8:18 kernel test robot
2019-04-26  6:14 ` Huang, Ying
2019-05-08  7:56   ` Huang, Ying
2019-05-24  7:46     ` Huang, Ying
2019-05-24 14:36       ` Josef Bacik [this message]
2019-05-27  0:38         ` Huang, Ying

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=20190524143558.mem7gircjjmut54f@MacBook-Pro-91.local \
    --to=josef@toxicpanda.com \
    --cc=dsterba@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=rong.a.chen@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=wqu@suse.com \
    --cc=ying.huang@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

all inboxes | Powered by JetHome®