From: michel.dagenais@polymtl.ca (Michel Dagenais)
Subject: [ltt-dev] sys time
Date: Fri, 17 Oct 2008 13:33:09 -0400 [thread overview]
Message-ID: <1224264789.16630.140.camel@localhost> (raw)
In-Reply-To: <8d94e9280810170940r7a0eff65se68d7636acbb0d33@mail.gmail.com>
On Fri, 2008-10-17 at 18:40 +0200, Gian Lorenzo Meocci wrote:
> I agree with you but this don't resolv my problem. Infact my problem
> is that "time" give me 1.74 sec of sys time when analising lttng-trace
> I obtain only 0.87.
The time command can be pretty far off when a process is making a lot of
system calls. It usually underestimates the user time, which is
consistent with what you are seeing. Basically, the kernel simply counts
a full jiffy for the process currently executing when the timer
generates an interrupt. If a process makes a lot of system calls, it
will often be scheduled at the beginning of a timer interval but will
quickly yield to another process and not be there at the timer
interrupt.
prev parent reply other threads:[~2008-10-17 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8d94e9280810170558j5b9ed8d1q7da37da677c7bf7d@mail.gmail.com>
2008-10-17 13:06 ` Gian Lorenzo Meocci
2008-10-17 15:26 ` Pierre-Marc Fournier
2008-10-17 16:28 ` Mathieu Desnoyers
2008-10-17 16:40 ` Gian Lorenzo Meocci
2008-10-17 17:33 ` Michel Dagenais [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=1224264789.16630.140.camel@localhost \
--to=michel.dagenais@polymtl.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