public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Huang Ying <ying.huang@intel.com>
Cc: Jason Low <jason.low2@hp.com>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>,
	mingo@kernel.org, dave@stgolabs.net
Subject: Re: [LKP] [mutex] 871a6bb4916: -1.8% will-it-scale.per_process_ops, -98.3% will-it-scale.time.voluntary_context_switches, +209.6% will-it-scale.time.involuntary_context_switches
Date: Mon, 16 Feb 2015 16:17:51 +0100	[thread overview]
Message-ID: <20150216151751.GE5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1423986414.5538.8.camel@intel.com>

On Sun, Feb 15, 2015 at 03:46:54PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
> commit 871a6bb4916fef3123b6ff749b0dc82680fb0d2a ("mutex: In mutex_spin_on_owner(), return true when owner changes")
> 
> 
> testbox/testcase/testparams: wsm/will-it-scale/performance-writeseek3
> 
> e07e0d4cb0c4bfe8  871a6bb4916fef3123b6ff749b  
> ----------------  --------------------------  
>          %stddev     %change         %stddev
>              \          |                \  
>   24972759 ±  2%     -98.3%     417134 ±  9%  will-it-scale.time.voluntary_context_switches
>       2223 ± 49%    +209.6%       6884 ± 10%  will-it-scale.time.involuntary_context_switches
>        542 ± 32%     +91.3%       1037 ±  0%  will-it-scale.time.system_time
>        186 ± 30%     +86.3%        347 ±  0%  will-it-scale.time.percent_of_cpu_this_job_got
>      26.11 ±  5%     -22.7%      20.18 ±  2%  will-it-scale.time.user_time
>       0.09 ±  1%     -18.2%       0.07 ±  1%  will-it-scale.scalability
>     783528 ±  0%      -1.8%     769550 ±  0%  will-it-scale.per_process_ops

>      12.27 ± 10%    +492.7%      72.73 ±  1%  perf-profile.cpu-cycles.mutex_optimistic_spin.__mutex_lock_slowpath.mutex_lock.generic_file_write_iter.new_sync_write
>       3.22 ± 26%   +1718.0%      58.50 ±  1%  perf-profile.cpu-cycles.osq_lock.mutex_optimistic_spin.__mutex_lock_slowpath.mutex_lock.generic_file_write_iter


Do you have the results for more/different performance tests for this
commit?

Jason mentioned seeing +5% on one (fserver).

So if, for multiple tests, we see an avg improvement, we might trade
that for this one regression.

If otoh we see a net negative, we'll have to go do something about this.


      reply	other threads:[~2015-02-16 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15  7:46 [LKP] [mutex] 871a6bb4916: -1.8% will-it-scale.per_process_ops, -98.3% will-it-scale.time.voluntary_context_switches, +209.6% will-it-scale.time.involuntary_context_switches Huang Ying
2015-02-16 15:17 ` Peter Zijlstra [this message]

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=20150216151751.GE5029@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=dave@stgolabs.net \
    --cc=jason.low2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mingo@kernel.org \
    --cc=ying.huang@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