From: Francis.Giraldeau@USherbrooke.ca (Francis Giraldeau)
Subject: [ltt-dev] Experiments on CPU time statistics
Date: Thu, 11 Nov 2010 12:50:29 -0500 [thread overview]
Message-ID: <20101111125029.18064gu6bt6eo084@www.usherbrooke.ca> (raw)
Hi,
I'm doing some experiments with CPU statistics, and I think that those
computed by lttv are wrong. I did 3 tests, and for each command the
time utility was used to get a baseline, and the command has been run
between lttctl -C and lttctl -D to get a tight window around the test
process.
=================================================
trace-bonnie.sh : start bonnie++ process for 10s
time statistics:
real 0m10.715s
user 0m0.420s
sys 0m6.350s
lttv statistics:
events count : 11088588
cpu time : 80.051904112
elapsed time? : 544.593369365
cumulative cpu time : 6.747053976
=================================================
sleep 1s : start a sleep of 1s
time statistics:
real 0m1.002s
user 0m0.000s
sys 0m0.000s
lttv statistics:
events count : 94929
cpu time : 7.841686487
elapsed time : 34.566952675
cumulative cpu time : 0.036465023
=================================================
trace-burn.sh 1s * 8 process simultan?s
time statistics:
real 0m1.031s
user 0m7.650s
sys 0m0.020s
lttv statistics:
events count : 95402
cpu time : 8.584145675
elapsed time : 33.845893813
cumulative cpu time : 0.037255816
=================================================
I was expecting lttv enlapsed time to be close to real time, lttv
cumulative cpu time to be greater or equal to lttv cpu time, and lttc
cpu time to match user + sys time. Does it make sens, or maybe I'm
getting something wrong?
Cheer,
Francis
next reply other threads:[~2010-11-11 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 17:50 Francis Giraldeau [this message]
2010-11-11 18:59 ` Mathieu Desnoyers
2010-11-11 19:23 ` Michel Dagenais
2010-11-11 21:05 ` Francis Giraldeau
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=20101111125029.18064gu6bt6eo084@www.usherbrooke.ca \
--to=francis.giraldeau@usherbrooke.ca \
/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