From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [btrfs] 302167c50b: fio.write_bw_MBps -12.4% regression
Date: Fri, 26 Apr 2019 14:14:11 +0800 [thread overview]
Message-ID: <87h8alqong.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20190203081802.GD10498@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
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?
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: 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, 26 Apr 2019 14:14:11 +0800 [thread overview]
Message-ID: <87h8alqong.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20190203081802.GD10498@shao2-debian> (kernel test robot's message of "Sun, 3 Feb 2019 16:18:02 +0800")
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?
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2019-04-26 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 8:18 [btrfs] 302167c50b: fio.write_bw_MBps -12.4% regression kernel test robot
2019-02-03 8:18 ` [LKP] " kernel test robot
2019-04-26 6:14 ` Huang, Ying [this message]
2019-04-26 6:14 ` Huang, Ying
2019-05-08 7:56 ` Huang, Ying
2019-05-08 7:56 ` [LKP] " Huang, Ying
2019-05-24 7:46 ` Huang, Ying
2019-05-24 7:46 ` [LKP] " Huang, Ying
2019-05-24 14:36 ` Josef Bacik
2019-05-27 0:38 ` Huang, Ying
2019-05-27 0:38 ` [LKP] " 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=87h8alqong.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.