mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: 0day robot <lkp@intel.com>, Chen Yu <yu.c.chen@intel.com>,
	Walter Mack <walter.mack@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, ying.huang@intel.com, feng.tang@intel.com,
	zhengjun.xing@linux.intel.com, fengwei.yin@intel.com,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Ingo Molnar <mingo@elte.hu>, Juri Lelli <juri.lelli@redhat.com>,
	Mel Gorman <mgorman@suse.de>,
	aubrey.li@linux.intel.com
Subject: Re: [sched/fair]  ddb3b1126f:  hackbench.throughput -25.9% regression
Date: Wed, 30 Mar 2022 16:48:05 -0700	[thread overview]
Message-ID: <7aa67fedb4b6dc9126bc59ee993fa18d0e472475.camel@linux.intel.com> (raw)
In-Reply-To: <20220330094632.GB6999@xsang-OptiPlex-9020>

On Wed, 2022-03-30 at 17:46 +0800, kernel test robot wrote:
> 
> Greeting,
> 
> FYI, we noticed a -25.9% regression of hackbench.throughput due to commit:
> 

Will try to check the regression seen.

Thanks.

Tim

> 
> 
> commit: 
>   d9ad181b93 ("sched/fair: Don't rely on ->exec_start for migration")
>   ddb3b1126f ("sched/fair: Simple runqueue order on migrate")
> 
> d9ad181b93f83b36 ddb3b1126fe93e8d6e059600488 
> ---------------- --------------------------- 
>          %stddev     %change         %stddev
>              \          |                \  
>      92566           -25.9%      68598 ±  2%  hackbench.throughput
>      85.50           +40.8%     120.35 ±  2%  hackbench.time.elapsed_time
>      85.50           +40.8%     120.35 ±  2%  hackbench.time.elapsed_time.max
>    9674391 ±  2%    +466.2%   54780205 ±  2%  hackbench.time.involuntary_context_switches
>       1240           +42.6%       1768 ±  3%  hackbench.time.system_time
>      89.58           +20.4%     107.85        hackbench.time.user_time
>   36626407          +270.2%  1.356e+08 ±  2%  hackbench.time.voluntary_context_switches
>    2500490 ±  3%     +78.2%    4456808 ±  3%  cpuidle..usage
>     118.45 ±  2%     +29.2%     153.02 ±  2%  uptime.boot
> 


  reply	other threads:[~2022-03-30 23:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 22:54 [PATCH 0/2] sched/fair: Fix starvation caused by task migration Tim Chen
2022-03-25 22:54 ` [PATCH 1/2] sched/fair: Don't rely on ->exec_start for migration Tim Chen
2022-03-25 22:54 ` [PATCH 2/2] sched/fair: Simple runqueue order on migrate Tim Chen
2022-03-29  9:03   ` Vincent Guittot
2022-03-31 11:47     ` Peter Zijlstra
2022-03-31 12:15       ` Vincent Guittot
2022-03-29 10:09   ` Abel Wu
2022-03-29 14:26     ` Tim Chen
2022-03-30  9:46   ` [sched/fair] ddb3b1126f: hackbench.throughput -25.9% regression kernel test robot
2022-03-30 23:48     ` Tim Chen [this message]
2022-04-01 18:04       ` Chen Yu

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=7aa67fedb4b6dc9126bc59ee993fa18d0e472475.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=mgorman@suse.de \
    --cc=mingo@elte.hu \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.org \
    --cc=walter.mack@intel.com \
    --cc=ying.huang@intel.com \
    --cc=yu.c.chen@intel.com \
    --cc=zhengjun.xing@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

Powered by JetHome