From: William Cohen <wcohen@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Slowness module generating for testsuite/systemtap.stress/current.stp due to elfutils-0.131
Date: Fri, 08 Feb 2008 13:20:00 -0000 [thread overview]
Message-ID: <47AC570C.80602@redhat.com> (raw)
I was looking through the nightly test results and I noticed that recently
systemtap.stress/current.stp times out on all the machine running nightly tests.
It uses to be that systemtap.stress/current.stp was a relatively quick test to run.
I looked through the nightly testing build that checks things out at 4:30 am EST
and it appears that stap is reasonably fast 20080124 then 2008125 it is
literally 30 times slower. Ran the following command with various versions of
systemtap in the testsuite directory:
/usr/bin/time ../stap
/home/wcohen/stap_testing_200802070930/src/testsuite/systemtap.stress/current.stp
-g -m x -v -c 'sleep 1'
Below is the table of results from the time command.
date output of time
20080124
6.23user 1.25system 0:11.84elapsed 63%CPU
(0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (406major+196130minor)pagefaults 0swaps
20080125
230.78user 1.37system 3:55.77elapsed 98%CPU
(0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (29major+213027minor)pagefaults 0swaps
The problem appear to be a huge amount of time spent in some of the rountines in
elfutils-0.131. Also see huge amount of time with elfutils-0.132. The same
systemtap code built elfutils-0.129 is much faster (30 times faster). Below is a
profiling data from oprofile showing the routines that the systemtap spends its
time in elfutils-0.132:
$ opreport -t1 ./stap -l
CPU: P4 / Xeon with 2 hyper-threads, speed 2793.08 MHz (estimated)
Counted GLOBAL_POWER_EVENTS events (time during which processor is not stopped)
with a unit mask of 0x01 (mandatory) count 100000
samples % image name symbol name
4355797 68.3146 libdw.so.1 relocate.5976
1679547 26.3414 libelf.so.1 gelf_getsymshndx
168836 2.6480 libc-2.5.so strcmp
94576 1.4833 libdw.so.1 anonymous symbol from section .plt
-Will
next reply other threads:[~2008-02-08 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 13:20 William Cohen [this message]
[not found] ` <y0mzlub4jwt.fsf@ton.toronto.redhat.com>
2008-02-08 21:17 ` [Forw:] " Roland McGrath
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=47AC570C.80602@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).