From: Eric Dumazet <dada1@cosmosbay.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dynamic linking files slow fork down significantly
Date: Sun, 04 Mar 2007 11:14:18 +0100 [thread overview]
Message-ID: <45EA9BFA.70401@cosmosbay.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0703040012070.26326@qynat.qvtvafvgr.pbz>
David Lang a écrit :
> On Sat, 3 Mar 2007, Eric Dumazet wrote:
>>
>> # time ldd -r ./groff
>> libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xf7e8f000)
>> libm.so.6 => /lib/tls/libm.so.6 (0xf7e6d000)
>> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7e62000)
>> libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
>> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xf7f4c000)
>> 0.00user 0.00system 0:00.00elapsed 50%CPU (0avgtext+0avgdata
>> 0maxresident)k
>> 0inputs+0outputs (0major+777minor)pagefaults 0swaps
>>
>> You can see 777 pagefaults instead of 696 on this example.
>
> the version of time on my system (debian 3.1) doesn't give me the cpu or
> pagefault info, just the times. where should I get the version that
> gives more info? (although I don't think I can apply it directly to my
> troubleshooting as the work is all being done in child processes).
time is a shell builtin.
But there is normally an /usr/bin/time standalone program.
# type time
time is a shell keyword
# time date
Sun Mar 4 12:15:54 CET 2007
real 0m0.003s
user 0m0.000s
sys 0m0.000s
# /usr/bin/time date
Sun Mar 4 12:15:56 CET 2007
0.00user 0.00system 0:00.00elapsed ?%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+192minor)pagefaults 0swaps
prev parent reply other threads:[~2007-03-04 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 0:53 dynamic linking files slow fork down significantly David Lang
2007-03-03 7:48 ` Eric Dumazet
2007-03-04 8:22 ` David Lang
2007-03-04 10:14 ` Eric Dumazet [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=45EA9BFA.70401@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@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