Home
last modified time | relevance | path

Searched refs:func_a (Results 1 – 25 of 102) sorted by relevance

12345

/NextBSD/cddl/contrib/dtracetoolkit/Examples/
HDpy_profile_example.txt25 [ ./func_slow.py:24 (func_a) ]
41 [ ./func_slow.py:24 (func_a) ]
53 [ ./func_slow.py:24 (func_a) ]
64 [ ./func_slow.py:18 (func_a) ]
82 [ ./func_slow.py:24 (func_a) ]
97 [ ./func_slow.py:24 (func_a) ]
112 [ ./func_slow.py:24 (func_a) ]
131 [ ./func_slow.py:24 (func_a) ]
147 [ ./func_slow.py:24 (func_a) ]
163 [ ./func_slow.py:24 (func_a) ]
[all …]
HDj_profile_example.txt28 Func_loop.func_a()V
40 Func_loop.func_a()V
52 Func_loop.func_a()V
64 Func_loop.func_a()V
76 Func_loop.func_a()V
88 Func_loop.func_a()V
100 Func_loop.func_a()V
112 showing func_b() and func_a() - as expected from the source to Func_loop.java.
127 Func_loop.func_a()V
139 Func_loop.func_a()V
[all …]
HDphp_cputime_example.txt12 func_abc.php func func_a 1
22 func_abc.php func func_a 74
31 func_abc.php func func_a 210
34 was one call each of func_a(), func_b() and func_c().
36 The exclusive subroutine on-CPU times show that func_a() spent around 74
43 func_a() spent around 210 microseconds. This inclusive time includes the time
44 spent in other functions called (including sleep), and since func_a() called
HDtcl_calldist_example.txt38 PID=16033, proc, func_a
139 PID=16033, cmd, func_a
145 PID=16033, proc, func_a
151 The exclusive function elapsed times show that each func_a took between 256
154 The inclusive elapsed times section shows that each func_a spent
156 any other commands or procedures called by func_a.
HDphp_calldist_example.txt12 func_abc.php, func, func_a
56 func_abc.php, func, func_a
62 In total, 3 subroutines were called, one each of func_a(), func_b() and
72 func_a() took between 2.1 seconds and 4.2 seconds to execute. This time
73 includes the time spent in other subroutines called, and since func_a() called
HDphp_cpudist_example.txt12 func_abc.php, func, func_a
56 func_abc.php, func, func_a
62 In total, 3 subroutines were called, one each of func_a(), func_b() and
73 microseconds on CPU; and func_a() took between 128 and 255 microseconds on
75 func_a() called func_b() which called func_c(), these times make sense.
HDtcl_cputime_example.txt30 16038 proc func_a 535521
45 16038 proc func_a 3226247
46 16038 cmd func_a 3226275
51 The exclusive function on-CPU times show that func_a spent around 0.5 seconds
56 total, including the time spent in other functions called, and since func_a
HDsh_cpudist_example.txt34 func_slow.sh, func, func_a
66 func_slow.sh, func, func_a
75 The exclusive function on-CPU times show that func_a() spent between
79 spent between 1.0 and 2.1 seconds on-CPU, and func_a() spent between 2.1
81 functions called, and since func_a() called func_b() which called func_c(),
HDjs_cputime_example.txt12 func_clock.html func func_a 5
31 func_clock.html func func_a 83465
42 func_clock.html func func_a 498142
53 The exclusive subroutine on-CPU times shows, amongst other results, that func_a
57 The inclusive subroutine on-CPU times show that func_a spent around 0.5
HDphp_flowtime_example.txt8 0 3646108339057 func_abc.php 9 -> func_a
19 0 3646111362370 func_abc.php 9 <- func_a
24 showing that func_a() began; slept, and returned from sleep; and then called
31 (skipping the header) reads as "the time from func_a() beginning to
HDtcl_calltime_example.txt30 16028 proc func_a 363
47 16028 proc func_a 3026545
48 16028 cmd func_a 3026572
59 that func_a took the most amount of time all up. This makes sense if you
HDpl_cputime_example.txt12 func_slow.pl sub func_a 1
19 func_slow.pl sub func_a 264193
28 func_slow.pl sub func_a 1601653
30 In total, 3 subroutines were called, one each of func_a(), func_b() and
33 The exclusive subroutine on-CPU times show that func_a() spent around 264.2 ms
38 on-CPU, func_b() spent around 1.3 seconds, and func_a() spent around 1.6
40 called, and since func_a() called func_b() which called func_c(), these
HDjs_calldist_example.txt39 func_clock.html, func, func_a
79 func_clock.html, func, func_a
104 can see in this example that func_a took between 16384 microseconds and 32767
107 The inclusive function elapsed times show that func_a took between 65536
HDphp_flowinfo_example.txt8 0 18422/1 9 func_abc.php:22 func -> func_a
19 0 18422/1 10 func_abc.php:20 func <- func_a
24 showing that func_a() began; slept, and returned from sleep; and then called
29 (skipping the header) reads as "the time from func_a() beginning to
HDrb_cputime_example.txt16 func_slow.rb func Object::func_a 1
40 func_slow.rb func Object::func_a 405946
56 func_slow.rb func Object::func_a 4417717
66 The exclusive function on-CPU times shows, amongst other results, that func_a
70 The inclusive function on-CPU times show that func_a spent around 4.4
HDtcl_procflow_example.txt11 0 16073 3904971509305 -> func_a
16 0 16073 3904974531014 <- func_a
21 procedure and then shows that func_a began, and then called func_b.
HDjs_cpudist_example.txt41 func_clock.html, func, func_a
82 func_clock.html, func, func_a
102 see here that func_a had four instances of being on-CPU between 16384
107 by those functions. You can see that here func_a had four instances of being
HDsh_cputime_example.txt12 func_slow.sh func func_a 1
27 func_slow.sh func func_a 269465
36 func_slow.sh func func_a 2205352
40 The exclusive function on-CPU times show that func_a() spent around 268.4 ms
45 seconds on-CPU, func_b() spent around 1.9 seconds, and func_a() spent around
47 called, and since func_a() called func_b() which called func_c(), these
/NextBSD/cddl/contrib/dtracetoolkit/Notes/
HDALLexclusive_notes.txt40 16 func_a()
47 23 func_a
49 func_a() calls func_b() which calls func_c(). Tracing the flow using
54 2 0 3052991099265 func_abc.sh 2 -> func_a
65 13 0 3052994131707 func_abc.sh 7 <- func_a
69 Exclusive function time for func_a() in the above output would be the
72 exclusive time for func_a() is the time from lines 2 to 4.
74 Looking back at the code, exclusive time for func_a() is the time spent
HDALLinclusive_notes.txt37 16 func_a()
44 23 func_a
46 func_a() calls func_b() which calls func_c(). Tracing the flow using
51 2 0 3052991099265 func_abc.sh 2 -> func_a
62 13 0 3052994131707 func_abc.sh 7 <- func_a
66 Inclusive function time for func_a() in the above output would be the
70 Looking back at the code, inclusive time for func_a() is the time spent
HDALLflow_notes.txt17 0 2963130861619 func_abc.pl -> func_a
22 0 2963133881174 func_abc.pl <- func_a
32 0 2963130861619 func_abc.pl -> func_a
36 0 2963133881174 func_abc.pl <- func_a
/NextBSD/cddl/contrib/dtracetoolkit/Code/Tcl/
HDfunc_abc.tcl14 proc func_a {} { procedure
20 func_a
/NextBSD/cddl/contrib/dtracetoolkit/Code/Ruby/
HDfunc_abc.rb14 def func_a method
20 func_a
/NextBSD/cddl/contrib/dtracetoolkit/Code/Perl/
HDfunc_abc.pl14 sub func_a { subroutine
20 func_a();
HDfunc_malloc.pl13 sub func_a { subroutine
18 func_a();

12345