LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [lkp-robot] [mm]  e27be240df:  will-it-scale.per_process_ops -27.2% regression
Date: Tue, 8 May 2018 13:26:40 -0400	[thread overview]
Message-ID: <20180508172640.GB24175@cmpxchg.org> (raw)
In-Reply-To: <20180508053451.GD30203@yexl-desktop>

Hello,

On Tue, May 08, 2018 at 01:34:51PM +0800, kernel test robot wrote:
> FYI, we noticed a -27.2% regression of will-it-scale.per_process_ops due to commit:
> 
> 
> commit: e27be240df53f1a20c659168e722b5d9f16cc7f4 ("mm: memcg: make sure memory.events is uptodate when waking pollers")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> in testcase: will-it-scale
> on test machine: 72 threads Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz with 128G memory
> with following parameters:
> 
> 	nr_task: 100%
> 	mode: process
> 	test: page_fault3
> 	cpufreq_governor: performance
> 
> test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
> test-url: https://github.com/antonblanchard/will-it-scale

This is surprising. Do you run these tests in a memory cgroup with a
limit set? Can you dump that cgroup's memory.events after the run?

Thanks

  reply	other threads:[~2018-05-08 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08  5:34 kernel test robot
2018-05-08 17:26 ` Johannes Weiner [this message]
2018-05-09  2:32   ` [LKP] " Aaron Lu
2018-05-09 15:02     ` Aaron Lu
2018-05-28  8:52   ` Aaron Lu
2018-05-29  8:48     ` Michal Hocko
2018-05-30  8:27       ` Aaron Lu
2018-06-01  7:11         ` [RFC PATCH] mem_cgroup: make sure moving_account, move_lock_task and stat_cpu in the same cacheline Aaron Lu

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=20180508172640.GB24175@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=xiaolong.ye@intel.com \
    --subject='Re: [lkp-robot] [mm]  e27be240df:  will-it-scale.per_process_ops -27.2% regression' \
    /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

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).