[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180508172640.GB24175@cmpxchg.org>
Date: Tue, 8 May 2018 13:26:40 -0400
From: Johannes Weiner <hannes@...xchg.org>
To: kernel test robot <xiaolong.ye@...el.com>
Cc: linux-kernel@...r.kernel.org, lkp@...org
Subject: Re: [lkp-robot] [mm] e27be240df: will-it-scale.per_process_ops
-27.2% regression
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
Powered by blists - more mailing lists