* Some preliminary instrumentation and analyst of systemtap compiling instrumentation scripts
@ 2018-10-04 16:08 William Cohen
0 siblings, 0 replies; only message in thread
From: William Cohen @ 2018-10-04 16:08 UTC (permalink / raw)
To: systemtap
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-10-04 16:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-04 16:08 Some preliminary instrumentation and analyst of systemtap compiling instrumentation scripts William Cohen
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).