All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: kernel test robot <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@linux.intel.com
Subject: Re: [slub shrink] 0f6934bf16: +191.9% vmstat.system.cs
Date: Thu, 16 Jan 2014 11:12:19 -0800	[thread overview]
Message-ID: <52D82F13.9070309@intel.com> (raw)
In-Reply-To: <20140116030744.GA19349@localhost>

On 01/15/2014 07:07 PM, kernel test robot wrote:
> 9a0bb2966efbf30  0f6934bf1695682e7ced973f6  
> ---------------  -------------------------  
>    8235933 ~ 2%     +80.6%   14872911 ~ 3%  lkp-sbx04/micro/will-it-scale/read2
>    8235933          +80.6%   14872911       TOTAL interrupts.RES
> 
> 9a0bb2966efbf30  0f6934bf1695682e7ced973f6  
> ---------------  -------------------------  
>     161531 ~ 7%    +191.9%     471544 ~ 9%  lkp-sbx04/micro/will-it-scale/read2
>     161531         +191.9%     471544       TOTAL vmstat.system.cs
> 
> 9a0bb2966efbf30  0f6934bf1695682e7ced973f6  
> ---------------  -------------------------  
>      32943 ~ 1%     +71.8%      56599 ~ 3%  lkp-sbx04/micro/will-it-scale/read2
>      32943          +71.8%      56599       TOTAL vmstat.system.in

I suspect that something is wrong with that system.  My 160-cpu system
does about 40,000 interrupts/sec and ~4300 context switches/sec when
running 160 read2_processes.  I wonder if you're hitting swap or the
dirty limits or something.  Are you running it with way more threads
than it has CPUs?

Also, are those will-it-scale tests the threaded or process versions?

  reply	other threads:[~2014-01-16 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  3:07 [slub shrink] 0f6934bf16: +191.9% vmstat.system.cs kernel test robot
2014-01-16 19:12 ` Dave Hansen [this message]
2014-01-17  0:26   ` Fengguang Wu
2014-01-17 13:00   ` Fengguang Wu
2014-01-29  8:26   ` Fengguang Wu

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=52D82F13.9070309@intel.com \
    --to=dave.hansen@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@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 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.