* Problem when profiling a process' running/sleeping/waiting time
@ 2013-01-09 10:56 Victor Jimenez
2013-06-17 7:20 ` Michael Ellerman
0 siblings, 1 reply; 2+ messages in thread
From: Victor Jimenez @ 2013-01-09 10:56 UTC (permalink / raw)
To: linux-perf-users
I am trying to profile a process in terms of running, sleeping and
waiting time. I am using kernel 3.6.6 running on an IBM POWER7 machine.
Initially, I decided to use a toy example where I would expect that the
process remains in running state most of the time. This is the code for
such a simple example:
int main() {
for (int i = 0; i < 1000000; i++)
for (int j = 0; j < 1000; j++);
}
I am using the following command line for reading kernel stats:
perf stat -e
"sched:sched_stat_runtime,sched:sched_stat_sleep,sched:sched_stat_wait, \
sched:sched_stat_iowait,sched:sched_stat_blocked" ./test
And these are the results that I obtain:
Performance counter stats for './test':
12,077,957,756 sched:sched_stat_runtime
169,892,740,990 sched:sched_stat_sleep
5,816,784 sched:sched_stat_wait
0 sched:sched_stat_iowait
0 sched:sched_stat_blocked
12.084706279 seconds time elapsed
I cannot really understand why the counter for sched_stat_sleep is so
high (even higher than sched_stat_runtime), especially for such a
CPU-bound workload.
Am I missing anything, or there could be a problem with sched_stat_sleep
counter?
Thank you,
Victor
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Problem when profiling a process' running/sleeping/waiting time
2013-01-09 10:56 Problem when profiling a process' running/sleeping/waiting time Victor Jimenez
@ 2013-06-17 7:20 ` Michael Ellerman
0 siblings, 0 replies; 2+ messages in thread
From: Michael Ellerman @ 2013-06-17 7:20 UTC (permalink / raw)
To: Victor Jimenez; +Cc: linux-perf-users
On Wed, 2013-01-09 at 11:56 +0100, Victor Jimenez wrote:
> I am trying to profile a process in terms of running, sleeping and
> waiting time. I am using kernel 3.6.6 running on an IBM POWER7 machine.
> Initially, I decided to use a toy example where I would expect that the
> process remains in running state most of the time. This is the code for
> such a simple example:
>
> int main() {
> for (int i = 0; i < 1000000; i++)
> for (int j = 0; j < 1000; j++);
> }
>
> I am using the following command line for reading kernel stats:
>
> perf stat -e
> "sched:sched_stat_runtime,sched:sched_stat_sleep,sched:sched_stat_wait, \
> sched:sched_stat_iowait,sched:sched_stat_blocked" ./test
>
> And these are the results that I obtain:
>
> Performance counter stats for './test':
>
> 12,077,957,756 sched:sched_stat_runtime
> 169,892,740,990 sched:sched_stat_sleep
> 5,816,784 sched:sched_stat_wait
> 0 sched:sched_stat_iowait
> 0 sched:sched_stat_blocked
>
> 12.084706279 seconds time elapsed
>
> I cannot really understand why the counter for sched_stat_sleep is so
> high (even higher than sched_stat_runtime), especially for such a
> CPU-bound workload.
>
> Am I missing anything, or there could be a problem with sched_stat_sleep
> counter?
Hi Victor,
Did you ever work out what was going on here?
cheers
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-06-17 7:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-09 10:56 Problem when profiling a process' running/sleeping/waiting time Victor Jimenez
2013-06-17 7:20 ` Michael Ellerman
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).