All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuyang Du <yuyang.du@intel.com>
To: lkp@lists.01.org
Subject: Re: [sched/numa] a43455a1d57: +94.1% proc-vmstat.numa_hint_faults_local
Date: Fri, 01 Aug 2014 07:58:25 +0800	[thread overview]
Message-ID: <20140731235825.GH28673@intel.com> (raw)
In-Reply-To: <20140801072911.GE19379@twins.programming.kicks-ass.net>

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

On Fri, Aug 01, 2014 at 09:29:11AM +0200, Peter Zijlstra wrote:
> On Fri, Aug 01, 2014 at 10:03:30AM +0800, Aaron Lu wrote:
> > > > > ebe06187bf2aec1  a43455a1d572daf7b730fe12e  
> > > > > ---------------  -------------------------  
> > > > >      94500 ~ 3%    +115.6%     203711 ~ 6%  ivb42/hackbench/50%-threads-pipe
> > > > >      67745 ~ 4%     +64.1%     111174 ~ 5%  lkp-snb01/hackbench/50%-threads-socket
> > > > >     162245 ~ 3%     +94.1%     314885 ~ 6%  TOTAL proc-vmstat.numa_hint_faults_local
> 
> > It means, for commit ebe06187bf2aec1, the number for
> > num_hint_local_faults is 94500 for ivb42 machine and 67745 for lkp-snb01
> > machine. The 3%, 4% following that number means the deviation of the
> > different runs to their average(we usually run it multiple times to
> > phase out possible sharp values). We should probably remove that
> > percentage, as they cause confusion if no detailed explanation and may
> > not mean much to the commit author and others(if the deviation is big
> > enough, we should simply drop that result).
> 
> Nah, variance is good, but the typical symbol would be +- or the fancy
> ±.
> 
> ~ when used as a unary op means 'approx' or 'about' or 'same order'
> ~ when used as a binary op means equivalence, a weaker equal, often in
> the vein of the unary op meaning.
> 
> Also see: http://en.wikipedia.org/wiki/Tilde#Mathematics
> 
> So while I think having a measure of variance is good, I think you
> picked entirely the wrong symbol.

Or, maybe you can use σ (lower case sigma) to indicate stddev, :)

WARNING: multiple messages have this Message-ID (diff)
From: Yuyang Du <yuyang.du@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Aaron Lu <aaron.lu@intel.com>, Rik van Riel <riel@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, jhladky@redhat.com,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [LKP] [sched/numa] a43455a1d57: +94.1% proc-vmstat.numa_hint_faults_local
Date: Fri, 1 Aug 2014 07:58:25 +0800	[thread overview]
Message-ID: <20140731235825.GH28673@intel.com> (raw)
In-Reply-To: <20140801072911.GE19379@twins.programming.kicks-ass.net>

On Fri, Aug 01, 2014 at 09:29:11AM +0200, Peter Zijlstra wrote:
> On Fri, Aug 01, 2014 at 10:03:30AM +0800, Aaron Lu wrote:
> > > > > ebe06187bf2aec1  a43455a1d572daf7b730fe12e  
> > > > > ---------------  -------------------------  
> > > > >      94500 ~ 3%    +115.6%     203711 ~ 6%  ivb42/hackbench/50%-threads-pipe
> > > > >      67745 ~ 4%     +64.1%     111174 ~ 5%  lkp-snb01/hackbench/50%-threads-socket
> > > > >     162245 ~ 3%     +94.1%     314885 ~ 6%  TOTAL proc-vmstat.numa_hint_faults_local
> 
> > It means, for commit ebe06187bf2aec1, the number for
> > num_hint_local_faults is 94500 for ivb42 machine and 67745 for lkp-snb01
> > machine. The 3%, 4% following that number means the deviation of the
> > different runs to their average(we usually run it multiple times to
> > phase out possible sharp values). We should probably remove that
> > percentage, as they cause confusion if no detailed explanation and may
> > not mean much to the commit author and others(if the deviation is big
> > enough, we should simply drop that result).
> 
> Nah, variance is good, but the typical symbol would be +- or the fancy
> ±.
> 
> ~ when used as a unary op means 'approx' or 'about' or 'same order'
> ~ when used as a binary op means equivalence, a weaker equal, often in
> the vein of the unary op meaning.
> 
> Also see: http://en.wikipedia.org/wiki/Tilde#Mathematics
> 
> So while I think having a measure of variance is good, I think you
> picked entirely the wrong symbol.

Or, maybe you can use σ (lower case sigma) to indicate stddev, :)

  reply	other threads:[~2014-07-31 23:58 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53d70ee6.JsUEmW5dWsv8dev+%fengguang.wu@intel.com>
2014-07-29  5:24 ` [sched/numa] a43455a1d57: +94.1% proc-vmstat.numa_hint_faults_local Aaron Lu
2014-07-29  5:24   ` [LKP] " Aaron Lu
2014-07-29  6:39   ` Rik van Riel
2014-07-29  6:39     ` [LKP] " Rik van Riel
2014-07-29  8:17     ` Peter Zijlstra
2014-07-29  8:17       ` [LKP] " Peter Zijlstra
2014-07-29 20:04       ` Rik van Riel
2014-07-29 20:04         ` [LKP] " Rik van Riel
2014-07-30  2:14         ` Aaron Lu
2014-07-30  2:14           ` [LKP] " Aaron Lu
2014-07-30 14:25           ` Rik van Riel
2014-07-30 14:25             ` [LKP] " Rik van Riel
2014-07-31  5:04             ` Aaron Lu
2014-07-31  5:04               ` [LKP] " Aaron Lu
2014-07-31  6:22               ` Rik van Riel
2014-07-31  6:22                 ` [LKP] " Rik van Riel
2014-07-31  6:53                 ` Aaron Lu
2014-07-31  6:53                   ` [LKP] " Aaron Lu
2014-07-31  6:42               ` Rik van Riel
2014-07-31  6:42                 ` [LKP] " Rik van Riel
2014-08-05 21:43               ` Rik van Riel
2014-08-05 21:43                 ` [LKP] " Rik van Riel
2014-07-31  8:33           ` Peter Zijlstra
2014-07-31  8:33             ` [LKP] " Peter Zijlstra
2014-07-31  8:56             ` Aaron Lu
2014-07-31  8:56               ` [LKP] " Aaron Lu
2014-07-31 10:42     ` Peter Zijlstra
2014-07-31 10:42       ` [LKP] " Peter Zijlstra
2014-07-31 15:57       ` Peter Zijlstra
2014-07-31 15:57         ` [LKP] " Peter Zijlstra
2014-07-31 16:16         ` Jirka Hladky
2014-07-31 16:16           ` [LKP] " Jirka Hladky
2014-07-31 16:27           ` Peter Zijlstra
2014-07-31 16:27             ` [LKP] " Peter Zijlstra
2014-07-31 16:39             ` Jirka Hladky
2014-07-31 16:39               ` [LKP] " Jirka Hladky
2014-07-31 17:37               ` Peter Zijlstra
2014-07-31 17:37                 ` [LKP] " Peter Zijlstra
2014-08-01 15:02                 ` Peter Zijlstra
2014-08-01 15:02                   ` [LKP] " Peter Zijlstra
2014-08-01 20:46           ` Davidlohr Bueso
2014-08-01 20:46             ` [LKP] " Davidlohr Bueso
2014-08-01 20:48             ` Davidlohr Bueso
2014-08-01 20:48               ` [LKP] " Davidlohr Bueso
2014-08-01 21:30             ` Jirka Hladky
2014-08-01 21:30               ` [LKP] " Jirka Hladky
2014-08-02  4:17               ` Rik van Riel
2014-08-02  4:17                 ` [LKP] " Rik van Riel
2014-08-02  5:28                 ` Jirka Hladky
2014-08-02  5:28                   ` [LKP] " Jirka Hladky
2014-08-02  4:26               ` Peter Zijlstra
2014-08-02  4:26                 ` [LKP] " Peter Zijlstra
2014-08-01  0:18       ` Davidlohr Bueso
2014-08-01  0:18         ` [LKP] " Davidlohr Bueso
2014-08-01  2:03       ` Aaron Lu
2014-08-01  2:03         ` [LKP] " Aaron Lu
2014-08-01  4:03         ` Davidlohr Bueso
2014-08-01  4:03           ` [LKP] " Davidlohr Bueso
2014-08-01  7:29           ` Peter Zijlstra
2014-08-01  7:29             ` [LKP] " Peter Zijlstra
2014-08-01  7:29         ` Peter Zijlstra
2014-08-01  7:29           ` [LKP] " Peter Zijlstra
2014-07-31 23:58           ` Yuyang Du [this message]
2014-07-31 23:58             ` Yuyang Du
2014-08-01  8:14           ` Fengguang Wu
2014-08-01  8:14             ` [LKP] " 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=20140731235825.GH28673@intel.com \
    --to=yuyang.du@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.