This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/10788] -t statistics report on derived statement probes instead of mark probes
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 16 Oct 2009 22:47:02 -0000
- Subject: [Bug translator/10788] -t statistics report on derived statement probes instead of mark probes
- References: <20091016124037.10788.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jistone at redhat dot com 2009-10-16 22:47 -------
(In reply to comment #0)
> When running with -t the statistics report only shows the statement probes that
> were derived from the mark probes. That makes it hard to see which is which.
>
> $ stap -t -e 'probe process("stap").mark("*_start") { log("start: " . $$name) }
> probe process("stap").mark("*_end") { log("end: " . $$name) }' -c "stap -e
> 'probe begin { exit() }'"
> [...]
> probe process("stap").statement(877442) (<input>:1:1), hits: 8, cycles:
> 2640min/5039avg/10040max
> probe process("stap").statement(127589) (<input>:1:67), hits: 4, cycles:
> 6840min/7907avg/8980max
We currently kludge the .mark names back in for listing mode, but I've been
thinking of ways to make this appear more naturally. I may take a stab at it to
address your concern here as well.
> Also I would have expected to see all statement probes for all resolved mark
> probes instead of one statement probe for each group of mark probes.
This is a "feature". The timing stats are deliberately merged for each probe
body, which is why you see only two groups of timing info. If you do this on
"probe begin,end,error {...}", you'll see "probe begin+2" in the timing stats.
We should at least have this count the # of expanded wildcards as well.
As an enhancement, maybe we could split up the timing info with additional "-t"
options. I'm not sure how much granularity we need between the current "time
each script-level probe body" and "time each resolved probe instance" -- maybe
just those two levels are enough.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10788
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.