Displaying 2 results from an estimated 2 matches for "libswduar".
2011 Jan 05
0
dtrace-discuss Digest, Vol 69, Issue 2
...zation to see how tightly-banded the times are. Perhaps
there''s some blocking I/O in some of your calls, for example, in which case
you might expect a wide difference with functions that don''t.
I''ve annotated your code to show what you''re actually doing:
pid$1:libswduar::entry
{
// Associative array indexing timestamps by function call
duarEntry[probefunc] = timestamp;
// Aggregation to count each function invoked
@duarCount[probefunc] = count();
}
pid$1:libswduar::return
{
// Compute elapsed time in milliseconds
this-&g...
2011 Jan 05
0
Understand the dtrace quantize output
...DTrace , I have written a script to time function calls
in our application library ,
Wanted to know how to interpret the output from quantize of the elapsed time
in each function call , here is a sample
Here is the entry and return function for the library that is being traced
pid$1:libswduar::entry
{
duarEntry[probefunc] = timestamp;
@duarCount[probefunc] = count();
}
pid$1:libswduar::return
{
this->elapsed = (timestamp - duarEntry[probefunc])/1000000;
@totduarTime[probefunc] = quantize(this->elapsed);
duarEntry[probefunc] = 0;
}...