All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [mm] c8c06efa8b5: -7.6% unixbench.score
Date: Fri, 09 Jan 2015 11:03:26 +0800	[thread overview]
Message-ID: <1420772606.6201.126.camel@linux.intel.com> (raw)
In-Reply-To: <1420771673.12346.16.camel@stgolabs.net>

[-- Attachment #1: Type: text/plain, Size: 2528 bytes --]

On Thu, 2015-01-08 at 18:47 -0800, Davidlohr Bueso wrote:
> On Thu, 2015-01-08 at 10:27 +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> > 
> > commit c8c06efa8b552608493b7066c234cfa82c47fcea ("mm: convert i_mmap_mutex to rwsem")
> > 
> > 
> > testbox/testcase/testparams: lituya/unixbench/performance-execl
> > 
> > 83cde9e8ba95d180  c8c06efa8b552608493b7066c2  
> > ----------------  --------------------------  
> >          %stddev     %change         %stddev
> >              \          |                \  
> >     721721 ±  1%    +303.6%    2913110 ±  3%  unixbench.time.voluntary_context_switches
> >      11767 ±  0%      -7.6%      10867 ±  1%  unixbench.score
> 
> I simply cannot reproduce this, not even on a large box.
> 
> mutex (83cde9e8ba95d180):
> run1:
> Execl Throughput                               3974.3 lps   (30.0 s, 2 samples)
> Voluntary context switches: 377039
> 
> run2:
> Execl Throughput                               4115.5 lps   (30.0 s, 2 samples)
> Voluntary context switches: 391260
> 
> run3:
> Execl Throughput                               4000.2 lps   (30.0 s, 2 samples)
> Voluntary context switches: 378674
> 
> rwsem (c8c06efa8b552608493b7066c2):
> run1:
> Execl Throughput                               4166.0 lps   (30.0 s, 2 samples)
> Voluntary context switches: 385740
> 
> run2:
> Execl Throughput                               4115.5 lps   (30.0 s, 2 samples)
> Voluntary context switches: 391260
> 
> run3:
> Execl Throughput                               4110.5 lps   (29.9 s, 2 samples)
> Voluntary context switches: 387053
> 
> Since throughput is in the ballpark, so is the benchmark score (in fact
> the rwsem score is slightly better).
> 
> Is this a one time thing or can you observe it again? Any special things
> you guys are doing when running the benchmark? Here are some things I've
> done: cpu gov set to performance, Unixbench taken from
> (http://byte-unixbench.googlecode.com/files/UnixBench5.1.3.tgz ), used
> default compiler options from unixbench Makefile (that is using the
> solaris 2 option). This pretty much matches the environment info you've
> provided. We've done this lock type comparison exercise plenty of times
> in the past, and I'm a bit surprised to see your numbers.

Is it possible for you to try the reproduce steps in the original
reporting email sent by me?  If you have any question on that steps,
feel free to ask.

Best Regards,
Huang, Ying




WARNING: multiple messages have this Message-ID (diff)
From: Huang Ying <ying.huang@linux.intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [mm] c8c06efa8b5: -7.6% unixbench.score
Date: Fri, 09 Jan 2015 11:03:26 +0800	[thread overview]
Message-ID: <1420772606.6201.126.camel@linux.intel.com> (raw)
In-Reply-To: <1420771673.12346.16.camel@stgolabs.net>

On Thu, 2015-01-08 at 18:47 -0800, Davidlohr Bueso wrote:
> On Thu, 2015-01-08 at 10:27 +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> > 
> > commit c8c06efa8b552608493b7066c234cfa82c47fcea ("mm: convert i_mmap_mutex to rwsem")
> > 
> > 
> > testbox/testcase/testparams: lituya/unixbench/performance-execl
> > 
> > 83cde9e8ba95d180  c8c06efa8b552608493b7066c2  
> > ----------------  --------------------------  
> >          %stddev     %change         %stddev
> >              \          |                \  
> >     721721 ±  1%    +303.6%    2913110 ±  3%  unixbench.time.voluntary_context_switches
> >      11767 ±  0%      -7.6%      10867 ±  1%  unixbench.score
> 
> I simply cannot reproduce this, not even on a large box.
> 
> mutex (83cde9e8ba95d180):
> run1:
> Execl Throughput                               3974.3 lps   (30.0 s, 2 samples)
> Voluntary context switches: 377039
> 
> run2:
> Execl Throughput                               4115.5 lps   (30.0 s, 2 samples)
> Voluntary context switches: 391260
> 
> run3:
> Execl Throughput                               4000.2 lps   (30.0 s, 2 samples)
> Voluntary context switches: 378674
> 
> rwsem (c8c06efa8b552608493b7066c2):
> run1:
> Execl Throughput                               4166.0 lps   (30.0 s, 2 samples)
> Voluntary context switches: 385740
> 
> run2:
> Execl Throughput                               4115.5 lps   (30.0 s, 2 samples)
> Voluntary context switches: 391260
> 
> run3:
> Execl Throughput                               4110.5 lps   (29.9 s, 2 samples)
> Voluntary context switches: 387053
> 
> Since throughput is in the ballpark, so is the benchmark score (in fact
> the rwsem score is slightly better).
> 
> Is this a one time thing or can you observe it again? Any special things
> you guys are doing when running the benchmark? Here are some things I've
> done: cpu gov set to performance, Unixbench taken from
> (http://byte-unixbench.googlecode.com/files/UnixBench5.1.3.tgz ), used
> default compiler options from unixbench Makefile (that is using the
> solaris 2 option). This pretty much matches the environment info you've
> provided. We've done this lock type comparison exercise plenty of times
> in the past, and I'm a bit surprised to see your numbers.

Is it possible for you to try the reproduce steps in the original
reporting email sent by me?  If you have any question on that steps,
feel free to ask.

Best Regards,
Huang, Ying




  reply	other threads:[~2015-01-09  3:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  2:27 [mm] c8c06efa8b5: -7.6% unixbench.score Huang Ying
2015-01-08  2:27 ` [LKP] " Huang Ying
2015-01-08  7:45 ` Davidlohr Bueso
2015-01-08  7:45   ` [LKP] " Davidlohr Bueso
2015-01-08  7:50   ` Davidlohr Bueso
2015-01-08  7:50     ` [LKP] " Davidlohr Bueso
2015-01-08  8:59     ` Davidlohr Bueso
2015-01-08  8:59       ` [LKP] " Davidlohr Bueso
2015-01-08 10:37       ` Peter Zijlstra
2015-01-08 10:37         ` [LKP] " Peter Zijlstra
2015-01-08  8:24   ` Huang Ying
2015-01-08  8:24     ` [LKP] " Huang Ying
2015-01-09  2:47 ` Davidlohr Bueso
2015-01-09  2:47   ` [LKP] " Davidlohr Bueso
2015-01-09  3:03   ` Huang Ying [this message]
2015-01-09  3:03     ` Huang Ying
2015-01-09  4:02     ` Davidlohr Bueso
2015-01-09  4:02       ` [LKP] " Davidlohr Bueso
2015-01-09  5:41       ` Huang Ying
2015-01-09  5:41         ` [LKP] " Huang Ying
2015-01-10  2:18         ` Davidlohr Bueso
2015-01-10  2:18           ` [LKP] " Davidlohr Bueso
2015-01-27  7:45       ` Huang Ying
2015-01-27  7:45         ` [LKP] " Huang Ying
2015-01-27 20:43         ` Davidlohr Bueso
2015-01-27 20:43           ` [LKP] " Davidlohr Bueso

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=1420772606.6201.126.camel@linux.intel.com \
    --to=ying.huang@linux.intel.com \
    --cc=lkp@lists.01.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 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.