fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
bendlas has quit [Write error: Connection reset by peer]
<fche>
agentzh, hi
bendlas has joined #systemtap
orivej_ has joined #systemtap
orivej has quit [Ping timeout: 245 seconds]
changcheng has joined #systemtap
orivej_ has quit [Ping timeout: 252 seconds]
hpt has joined #systemtap
<agentzh>
fche: hey
sscox has quit [Ping timeout: 268 seconds]
hpt has quit [Ping timeout: 264 seconds]
hpt has joined #systemtap
hpt has quit [Ping timeout: 246 seconds]
orivej has joined #systemtap
mjw has joined #systemtap
aryehw has joined #systemtap
aryehw_ has joined #systemtap
khaled has joined #systemtap
wcohen has quit [Ping timeout: 245 seconds]
aryehw_ has quit [Quit: Leaving]
bsingh has joined #systemtap
bsingh has quit [Client Quit]
khaled has quit [Ping timeout: 245 seconds]
sscox has joined #systemtap
wcohen has joined #systemtap
changcheng has quit [Ping timeout: 245 seconds]
changcheng has joined #systemtap
sapatel has joined #systemtap
tromey has joined #systemtap
Guest88210 has quit [Ping timeout: 258 seconds]
Guest88210 has joined #systemtap
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #systemtap
<DUKENUKEM>
hey guys
<DUKENUKEM>
at the end of the systemtap run when it gives a little summary of your probes
<DUKENUKEM>
hits/cycles/variance/etc
<DUKENUKEM>
what is the cycles value? how long it took for the function to finish?
<DUKENUKEM>
currently i am timing function runtimes to look for a bottleneck with systemtap
<DUKENUKEM>
using return probes and entry gettimeofday_ns
<DUKENUKEM>
and it seems to work pretty well
<DUKENUKEM>
but i was just wondering if systemtap was already showing me this information
<fche>
cycles = low level rdtsc oriented numbers
<fche>
but stap estimates -its own- execution times, not that of the threads / programs that its probes are inserted in