From: "Huang\, Ying" <ying.huang@intel.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: kernel test robot <rong.a.chen@intel.com>
Cc: David Sterba <dsterba@suse.com>, <lkp@01.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [btrfs] c8eaeac7b7: aim7.jobs-per-min -11.7% regression
Date: Wed, 29 May 2019 16:42:22 +0800 [thread overview]
Message-ID: <87blzl7itt.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20190513025004.GG31424@shao2-debian> (kernel test robot's message of "Mon, 13 May 2019 10:50:04 +0800")
Hi, Josef,
kernel test robot <rong.a.chen@intel.com> writes:
> Greeting,
>
> FYI, we noticed a -11.7% regression of aim7.jobs-per-min due to commit:
>
>
> commit: c8eaeac7b734347c3afba7008b7af62f37b9c140 ("btrfs: reserve delalloc metadata differently")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: aim7
> on test machine: 40 threads Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with 384G memory
> with following parameters:
>
> disk: 4BRD_12G
> md: RAID0
> fs: btrfs
> test: disk_rr
> load: 1500
> cpufreq_governor: performance
>
> test-description: AIM7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of multiuser system.
> test-url: https://sourceforge.net/projects/aimbench/files/aim-suite7/
Here's another regression, do you have time to take a look at this?
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2019-05-29 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 2:50 [btrfs] c8eaeac7b7: aim7.jobs-per-min -11.7% regression kernel test robot
2019-05-29 8:42 ` Huang, Ying [this message]
2019-06-11 0:52 ` [LKP] " Huang, Ying
2019-06-21 0:48 ` Huang, Ying
2019-06-25 14:22 ` Josef Bacik
2019-06-26 2:39 ` Rong Chen
2019-06-26 3:17 ` Josef Bacik
2019-06-26 3:31 ` Rong Chen
2019-07-08 7:08 ` Huang, Ying
2019-07-22 8:03 ` 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=87blzl7itt.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=josef@toxicpanda.com \
--cc=rong.a.chen@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;
as well as URLs for NNTP newsgroup(s).