From: Mel Gorman <mgorman@suse.de>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Julia Lawall <Julia.Lawall@inria.fr>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, lkp@intel.com,
ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@intel.com, aubrey.li@linux.intel.com,
yu.c.chen@intel.com
Subject: Re: [sched/fair] d8fcb81f1a: netperf.Throughput_tps -16.9% regression
Date: Mon, 2 Nov 2020 11:00:08 +0000 [thread overview]
Message-ID: <20201102110008.GA3306@suse.de> (raw)
In-Reply-To: <20201101082452.GC31092@shao2-debian>
On Sun, Nov 01, 2020 at 04:24:52PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -16.9% regression of netperf.Throughput_tps due to commit:
>
>
> commit: d8fcb81f1acf651a0e50eacecca43d0524984f87 ("sched/fair: Check for idle core in wake_affine")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/core
>
>
> in testcase: netperf
> on test machine: 144 threads Intel(R) Xeon(R) Gold 5318H CPU @ 2.50GHz with 128G memory
> with following parameters:
>
> ip: ipv4
> runtime: 300s
> nr_threads: 25%
> cluster: cs-localhost
> test: SCTP_RR
> cpufreq_governor: performance
> ucode: 0x700001c
>
> test-description: Netperf is a benchmark that can be use to measure various aspect of networking performance.
> test-url: http://www.netperf.org/netperf/
>
> In addition to that, the commit also has significant impact on the following tests:
>
> +------------------+------------------------------------------------------------------------+
> | testcase: change | aim7: aim7.jobs-per-min 8.7% improvement |
> | test machine | 144 threads Intel(R) Xeon(R) Gold 5318H CPU @ 2.50GHz with 128G memory |
> | test parameters | cpufreq_governor=performance |
> | | disk=1BRD_48G |
> | | fs=xfs |
> | | load=600 |
> | | test=sync_disk_rw |
> | | ucode=0x700001c |
> +------------------+------------------------------------------------------------------------+
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>
I know I ran tests against this patch in general and gave an Ack but
these cases were not covered by me. For netperf, I neither vary the number
of threads nor did I cover SCTP_RR so this could be an example of where
the patch is a loss. I also had run reaim but not specifically for one
sub-test like this does and the generation of machines used was much
older than Gold 5318H. Grid or no grid, complete coverage is a challenge
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2020-11-02 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 8:24 [sched/fair] d8fcb81f1a: netperf.Throughput_tps -16.9% regression kernel test robot
2020-11-02 11:00 ` Mel Gorman [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-09 6:25 kernel test robot
2021-03-09 6:25 ` kernel test robot
2021-06-02 1:48 ` Xing Zhengjun
2021-06-02 6:17 ` Julia Lawall
2021-06-02 7:21 ` Julia Lawall
2021-06-02 8:34 ` Xing Zhengjun
2021-06-02 14:19 ` Julia Lawall
2021-06-03 7:55 ` Xing Zhengjun
2021-06-03 8:38 ` Julia Lawall
2021-06-06 16:13 ` Julia Lawall
2021-09-03 6:33 ` Xing Zhengjun
2021-09-03 7:49 ` Julia Lawall
2021-09-15 8:22 ` Julia Lawall
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=20201102110008.GA3306@suse.de \
--to=mgorman@suse.de \
--cc=Julia.Lawall@inria.fr \
--cc=aubrey.li@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=peterz@infradead.org \
--cc=rong.a.chen@intel.com \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=yu.c.chen@intel.com \
--cc=zhengjun.xing@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 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.