From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "José Simão" <jose.m.simao@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: observations at periodic intervals
Date: Mon, 9 Nov 2015 12:00:16 -0300 [thread overview]
Message-ID: <20151109150016.GB4715@kernel.org> (raw)
In-Reply-To: <CAJ38vxsyHv4+SDHhP_YKMFAf-5i_S2Hp+T-0oc4RtsEgdGFodg@mail.gmail.com>
Em Fri, Nov 06, 2015 at 09:06:14PM +0000, José Simão escreveu:
> Dear user of linux-perf-users@vger.kernel.org,
>
> When using the -I option of 'stat' to periodically collect the value
> of performance counters (e.g. perf stat -e cache-misses -I 500 cmd)
> the reported value at each internal (500ms in the example) is how much
> the selected counter increased since the last observation?
>
> I assume it is because the values are not monotonically increasing.
From 'perf stat --help' /-I
-I msecs, --interval-print msecs
Print count deltas every N milliseconds (minimum: 100ms)
example: perf stat -I 1000 -e cycles -a sleep 5
This is also available via 'man perf-stat'
So, yes, your observation is correct, those are deltas.
- Arnaldo
prev parent reply other threads:[~2015-11-09 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 21:06 observations at periodic intervals José Simão
2015-11-09 15:00 ` Arnaldo Carvalho de Melo [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=20151109150016.GB4715@kernel.org \
--to=acme@kernel.org \
--cc=jose.m.simao@gmail.com \
--cc=linux-perf-users@vger.kernel.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 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).