From: Milian Wolff <milian.wolff@kdab.com>
To: linux-perf-users@vger.kernel.org
Cc: acme@kernel.org, namhyung@kernel.org, Jiri Olsa <jolsa@redhat.com>
Subject: measuring system wide CPU usage ignoring idle process
Date: Mon, 20 Nov 2017 15:00:46 +0100 [thread overview]
Message-ID: <3344812.IFj9h2T05j@agathebauer> (raw)
Hey all,
colleagues of mine just brought this inconvenient perf stat behavior to my
attention:
$ perf stat -a -e cpu-clock,task-clock,cycles,instructions sleep 1
Performance counter stats for 'system wide':
4004.501439 cpu-clock (msec) # 4.000 CPUs utilized
4004.526474 task-clock (msec) # 4.000 CPUs utilized
945,906,029 cycles # 0.236 GHz
461,861,241 instructions # 0.49 insn per cycle
1.001247082 seconds time elapsed
This shows that cpu-clock and task-clock are incremented also for the idle
processes. Is there some trick to exclude that time, such that the CPU
utilization drops below 100% when doing `perf stat -a`?
Or should one ignore these clock measurements for system wide stats and only
look at the cycles/instructions etc.? This does go somewhat in the direction
of http://www.brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html
anyways, so I'm not opposed to this.
Thanks
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
next reply other threads:[~2017-11-20 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 14:00 Milian Wolff [this message]
2017-11-20 14:29 ` measuring system wide CPU usage ignoring idle process Jiri Olsa
2017-11-20 20:24 ` Milian Wolff
2017-11-20 23:44 ` Jiri Olsa
2017-11-23 13:40 ` Milian Wolff
2017-11-23 14:09 ` Jiri Olsa
2017-11-23 14:21 ` Jiri Olsa
2017-11-23 14:42 ` Arnaldo Carvalho de Melo
2017-11-23 15:12 ` Jiri Olsa
2017-11-23 18:59 ` Arnaldo Carvalho de Melo
2017-11-24 8:14 ` Jiri Olsa
2017-11-23 15:15 ` Peter Zijlstra
2018-04-17 13:41 ` Arnaldo Carvalho de Melo
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=3344812.IFj9h2T05j@agathebauer \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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 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.