linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cody P Schafer <devel-lists@codyps.com>
To: Peipei Wang <wangpeipei.90@gmail.com>
Cc: perf group <linux-perf-users@vger.kernel.org>
Subject: Re: What does the "scaled from 66.58%" means?? What is scaled??
Date: Mon, 24 Jun 2013 16:36:06 -0700	[thread overview]
Message-ID: <51C8D7E6.2040401@codyps.com> (raw)
In-Reply-To: <CAEuYUeq_fT+rz_hoMTqSX14EL0Z1CdAaEc8C5zyxXfgG=H7=bg@mail.gmail.com>

On 06/24/2013 03:37 PM, Peipei Wang wrote:
> perf stat -B dd if=/dev/zero of=/dev/null count=1000000
>
> 1000000+0 records in
> 1000000+0 records out
> 512000000 bytes (512 MB) copied, 0.956217 s, 535 MB/s
>
>   Performance counter stats for 'dd if=/dev/zero of=/dev/null count=1000000':
>
>              5,099 cache-misses             #      0.005 M/sec (scaled
> from 66.58%)
>            235,384 cache-references         #      0.246 M/sec (scaled
> from 66.56%)
>          9,281,660 branch-misses            #      3.858 %     (scaled
> from 33.50%)
>        240,609,766 branches                 #    251.559 M/sec (scaled
> from 33.66%)
>      1,403,561,257 instructions             #      0.679 IPC   (scaled
> from 50.23%)
>      2,066,201,729 cycles                   #   2160.227 M/sec (scaled
> from 66.67%)
 > ...
> Can anyone explain to me the meaning of "scaled from", and from which
> get the 66.58% or 33.50%??

The scaling indicates that we had to time slice performance events 
because we couldn't enable them all at once.

The 33% indicates that that event was only active 33% of the time, so 
we've scaled it (multiplied by 3, in this case) with the assumption that 
it would show up with the same frequency during the times it was 
disabled. (Same for 66%).

      reply	other threads:[~2013-06-24 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 22:37 What does the "scaled from 66.58%" means?? What is scaled?? Peipei Wang
2013-06-24 23:36 ` Cody P Schafer [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=51C8D7E6.2040401@codyps.com \
    --to=devel-lists@codyps.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=wangpeipei.90@gmail.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;
as well as URLs for NNTP newsgroup(s).