All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [kernel] fc7f0dd3817: -2.1% will-it-scale.per_thread_ops
Date: Tue, 27 Jan 2015 09:17:11 +0800	[thread overview]
Message-ID: <1422321431.24875.35.camel@intel.com> (raw)
In-Reply-To: <23E39399-135D-485B-8AF6-FB5D2B874A9A@me.com>

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

On Mon, 2015-01-26 at 12:36 -0700, Louis Langholtz wrote:
> Hi Huang (and others on the lkp(a)01.org mailing list),
> 
> Not sure how to interpret the numbers you provided. Is there a web
> page that you would suggest looking at that I might read up?

Sorry we have no web page.  Most words in the email is straightforward.

testbox/testcase/testparams: lituya/will-it-scale/powersave-mmap2

test machine: lituya, it is a Haswell-EP machine
test case: will-it-scale (a benchmark to measure performance via
invoking some system call in a loop)
test params: powersave-mmap2: powersave CPU frequency governor is used,
the sub test case in will-it-scale is: mmap2

7ad4b4ae5757b896  fc7f0dd381720ea5ee5818645f  

Here is the parent commit ID and the commit ID for your patch.

----------------  --------------------------  
         %stddev     %change         %stddev
             \          |                \  
    252693 ±  0%      -2.2%     247031 ±  0%  will-it-scale.per_thread_ops

252693 and 247031 is the score from the benchmark
0% is the standard deviation for the score
-2.2% is the change between the parent and your patch.

> It wouldn't surprise me if the changes made resulted in slightly
> decreased performance - the number of commands shown in disassembly of
> the code not surprisingly increases.

Best Regards,
Huang, Ying

> On Jan 21, 2015, at 7:39 PM, Huang Ying <ying.huang@intel.com> wrote:
> 
> > FYI, we noticed the below changes on
> > 
> > commit fc7f0dd381720ea5ee5818645f7d0e9dece41cb0 ("kernel: avoid overflow in cmp_range")
> > 
> > 
> > testbox/testcase/testparams: lituya/will-it-scale/powersave-mmap2
> > 
> > 7ad4b4ae5757b896  fc7f0dd381720ea5ee5818645f  
> > ----------------  --------------------------  
> >         %stddev     %change         %stddev
> >             \          |                \  ...
> > Disclaimer:
> > Results have been estimated based on internal Intel analysis and are provided
> > for informational purposes only. Any difference in system hardware or software
> > design or configuration may affect actual performance.
> > 
> > 
> > Thanks,
> > Huang, Ying
> > 
> > <job.yaml><reproduce.txt>_______________________________________________
> > LKP mailing list
> > LKP(a)linux.intel.com
> > 
> 



      reply	other threads:[~2015-01-27  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  2:39 [kernel] fc7f0dd3817: -2.1% will-it-scale.per_thread_ops Huang Ying
2015-01-22  2:39 ` [LKP] " Huang Ying
2015-01-26 19:36 ` Louis Langholtz
2015-01-27  1:17   ` Huang Ying [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=1422321431.24875.35.camel@intel.com \
    --to=ying.huang@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.