From: William Cohen <wcohen@redhat.com>
To: systemtap@sourceware.org
Subject: Some preliminary instrumentation and analyst of systemtap compiling instrumentation scripts
Date: Thu, 04 Oct 2018 16:08:00 -0000 [thread overview]
Message-ID: <73697cfc-00da-f478-13dd-a747d39aa2e8@redhat.com> (raw)
Hi,
I have been expanding the example how systemtap could be useful. I just added an example that makes use of the systemtap user-space markers to record the amount of time that each phase of systemtap takes:
https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=blob;f=testsuite/systemtap.examples/apps/stap_time.stp
The goal of this script is to make it easy to collect data on how long it takes for the various example scripts to build and determine if there are any problematic ones that need to be looked at more closely. I have put the raw data, gnuplot scripts, and resulting svg graphs on:
http://people.redhat.com/wcohen/stap_profile/
The readme.txt in the directory describe the files.
One can look at the .svg and then the corresponding .dat to determine which examples have the long elaboration (pass2) and compile (pass4) times.
The reason for the long pass1 times for the x86_64_times.dat is due to the huge number of qemu tapsets on the machine 84MB vs 7.1MB on the guest_x86_64 machine.
I am looking through the graphs and matching up the various peaks with the original *.dat files.
-Will
reply other threads:[~2018-10-04 16:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=73697cfc-00da-f478-13dd-a747d39aa2e8@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).