The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: Re: [lkp] [mm] 795ae7a0de: pixz.throughput -9.1% regression
Date: Mon, 6 Jun 2016 16:53:07 +0800	[thread overview]
Message-ID: <20160606085307.GB2926@yexl-desktop> (raw)
In-Reply-To: <20160603222109.GA12579@cmpxchg.org>

On Fri, Jun 03, 2016 at 06:21:09PM -0400, Johannes Weiner wrote:
>On Thu, Jun 02, 2016 at 12:07:06PM -0400, Johannes Weiner wrote:
>> Hi,
>> 
>> On Thu, Jun 02, 2016 at 02:45:07PM +0800, kernel test robot wrote:
>> > FYI, we noticed pixz.throughput -9.1% regression due to commit:
>> > 
>> > commit 795ae7a0de6b834a0cc202aa55c190ef81496665 ("mm: scale kswapd watermarks in proportion to memory")
>> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> > 
>> > in testcase: pixz
>> > on test machine: ivb43: 48 threads Ivytown Ivy Bridge-EP with 64G memory with following parameters: cpufreq_governor=performance/nr_threads=100%
>> 
>> Xiaolong, thanks for the report.
>> 
>> It looks like the regression stems from a change in NUMA placement:
>
>Scratch that, I was misreading the test results. It's just fewer
>allocations in general that happen during the fixed testing time.
>
>I'm stumped by this report. All this patch does other than affect page
>reclaim (which is not involved here) is increase the size of the round
>robin batches in the fair zone allocator. That should *reduce* work in
>the page allocator, if anything.
>
>But I also keep failing to reproduce this - having tried it on the
>third machine now - neither pixz nor will-it-scale/page_fault1 give me
>that -8-9% regression:
>
>4.5.0-02574-g3ed3a4f:
>PIXZ-good.log:throughput: 39908733.604941994
>PIXZ-good.log:throughput: 37067947.25049969
>PIXZ-good.log:throughput: 38604938.39131216
>
>4.5.0-02575-g795ae7a:
> PIXZ-bad.log:throughput: 39489120.87179377
> PIXZ-bad.log:throughput: 39307299.288432725
> PIXZ-bad.log:throughput: 38795994.3329781
>
>Is this reliably reproducible with 3ed3a4f vs 795ae7a?

Yes, it can be stably reproduced in LKP environment, I've run 3ed3a4f0ddffece9 
for 4 times, and 795ae7a0de6b834a0cc202aa55 for 7 times.

3ed3a4f0ddffece9 795ae7a0de6b834a0cc202aa55
---------------- --------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
           :4           50%           2:7     kmsg.Spurious_LAPIC_timer_interrupt_on_cpu
         %stddev     %change         %stddev
             \          |                \
  78505362 ±  0%      -9.2%   71298182 ±  0%  pixz.throughput


>
>Could I ask you to retry the test with Linus's current head as well as
>with 795ae7a reverted on top of it? (It's a clean revert.)
>

Sure, I have queued the test tasks for them, will update the comparison
once I get the results.

Thanks,
Xiaolong

>Thanks

  reply	other threads:[~2016-06-06  8:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <574fd097.Frf8OIpckXVh1oaw%xiaolong.ye@intel.com>
2016-06-02  6:45 ` [lkp] [mm] 795ae7a0de: pixz.throughput -9.1% regression kernel test robot
2016-06-02 16:07   ` Johannes Weiner
2016-06-03  2:25     ` Ye Xiaolong
2016-06-03  9:00     ` Mel Gorman
2016-06-03 22:21     ` Johannes Weiner
2016-06-06  8:53       ` Ye Xiaolong [this message]
2016-06-07  4:48         ` [LKP] " Ye Xiaolong
2016-06-07 21:56           ` Johannes Weiner
2016-06-08  5:37             ` Ye Xiaolong
2016-06-22 21:24               ` Johannes Weiner

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=20160606085307.GB2926@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mgorman@suse.de \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.org \
    /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