| /netbsd-src/external/cddl/dtracetoolkit/dist/Docs/Examples/ |
| H A D | py_profile_example.txt | 21 [ ./func_slow.py:16 (func_b) ]
37 [ ./func_slow.py:16 (func_b) ]
49 [ ./func_slow.py:10 (func_b) ]
78 [ ./func_slow.py:10 (func_b) ]
93 [ ./func_slow.py:10 (func_b) ]
108 [ ./func_slow.py:10 (func_b) ]
127 [ ./func_slow.py:16 (func_b) ]
143 [ ./func_slow.py:16 (func_b) ]
159 [ ./func_slow.py:16 (func_b) ]
171 [ ./func_slow.py:10 (func_b) ]
[all …]
|
| H A D | j_profile_example.txt | 27 Func_loop.func_b()V
39 Func_loop.func_b()V
51 Func_loop.func_b()V
63 Func_loop.func_b()V
75 Func_loop.func_b()V
87 Func_loop.func_b()V
99 Func_loop.func_b()V
112 showing func_b() and func_a() - as expected from the source to Func_loop.java.
126 Func_loop.func_b()V
138 Func_loop.func_b()V
[all …]
|
| H A D | php_cputime_example.txt | 13 func_abc.php func func_b 1
21 func_abc.php func func_b 25
29 func_abc.php func func_b 87
34 was one call each of func_a(), func_b() and func_c().
37 microseconds on-CPU, func_b() spent 25 microseconds on-CPU, and func_c() spent
42 microseconds on-CPU, func_b() spent around 87 microseconds on-CPU and
45 func_b() which called func_c(), these times make perfect sense.
|
| H A D | php_calldist_example.txt | 18 func_abc.php, func, func_b
44 func_abc.php, func, func_b
62 In total, 3 subroutines were called, one each of func_a(), func_b() and
71 seconds and 1 second, func_b() took between 1 second and 2.1 seconds, and
74 func_b() which called func_c(), these times make sense.
|
| H A D | tcl_cputime_example.txt | 31 16038 proc func_b 1071082
43 16038 proc func_b 2690525
44 16038 cmd func_b 2690568
52 on-CPU, func_b spent about 1.0 seconds, and func_c, 1.6 seconds. This excludes
57 called func_b which called func_c, these times make sense.
|
| H A D | php_cpudist_example.txt | 18 func_abc.php, func, func_b
50 func_abc.php, func, func_b
62 In total, 3 subroutines were called, one each of func_a(), func_b() and
72 took between 16 and 31 microseconds on CPU; func_b() took between 64 and 127
75 func_a() called func_b() which called func_c(), these times make sense.
|
| H A D | pl_cputime_example.txt | 13 func_slow.pl sub func_b 1
20 func_slow.pl sub func_b 538498
27 func_slow.pl sub func_b 1337459
30 In total, 3 subroutines were called, one each of func_a(), func_b() and
34 on-CPU, func_b() spent 538.5 ms, and func_c() spent 799.0 ms. This exclusive
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
|
| H A D | sh_cputime_example.txt | 13 func_slow.sh func func_b 1
28 func_slow.sh func func_b 670372
35 func_slow.sh func func_b 1934839
41 on-CPU, func_b() spent 670.3 ms, and func_c() spent 1259 ms. This exclusive
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
|
| H A D | tcl_procflow_example.txt | 12 0 16073 3904972511039 -> func_b
15 0 16073 3904974531008 <- func_b
21 procedure and then shows that func_a began, and then called func_b.
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Examples/ |
| H A D | py_profile_example.txt | 21 [ ./func_slow.py:16 (func_b) ]
37 [ ./func_slow.py:16 (func_b) ]
49 [ ./func_slow.py:10 (func_b) ]
78 [ ./func_slow.py:10 (func_b) ]
93 [ ./func_slow.py:10 (func_b) ]
108 [ ./func_slow.py:10 (func_b) ]
127 [ ./func_slow.py:16 (func_b) ]
143 [ ./func_slow.py:16 (func_b) ]
159 [ ./func_slow.py:16 (func_b) ]
171 [ ./func_slow.py:10 (func_b) ]
[all …]
|
| H A D | j_profile_example.txt | 27 Func_loop.func_b()V
39 Func_loop.func_b()V
51 Func_loop.func_b()V
63 Func_loop.func_b()V
75 Func_loop.func_b()V
87 Func_loop.func_b()V
99 Func_loop.func_b()V
112 showing func_b() and func_a() - as expected from the source to Func_loop.java.
126 Func_loop.func_b()V
138 Func_loop.func_b()V
[all …]
|
| H A D | php_cputime_example.txt | 13 func_abc.php func func_b 1
21 func_abc.php func func_b 25
29 func_abc.php func func_b 87
34 was one call each of func_a(), func_b() and func_c().
37 microseconds on-CPU, func_b() spent 25 microseconds on-CPU, and func_c() spent
42 microseconds on-CPU, func_b() spent around 87 microseconds on-CPU and
45 func_b() which called func_c(), these times make perfect sense.
|
| H A D | php_calldist_example.txt | 18 func_abc.php, func, func_b
44 func_abc.php, func, func_b
62 In total, 3 subroutines were called, one each of func_a(), func_b() and
71 seconds and 1 second, func_b() took between 1 second and 2.1 seconds, and
74 func_b() which called func_c(), these times make sense.
|
| H A D | tcl_cputime_example.txt | 31 16038 proc func_b 1071082
43 16038 proc func_b 2690525
44 16038 cmd func_b 2690568
52 on-CPU, func_b spent about 1.0 seconds, and func_c, 1.6 seconds. This excludes
57 called func_b which called func_c, these times make sense.
|
| H A D | php_cpudist_example.txt | 18 func_abc.php, func, func_b
50 func_abc.php, func, func_b
62 In total, 3 subroutines were called, one each of func_a(), func_b() and
72 took between 16 and 31 microseconds on CPU; func_b() took between 64 and 127
75 func_a() called func_b() which called func_c(), these times make sense.
|
| H A D | pl_cputime_example.txt | 13 func_slow.pl sub func_b 1
20 func_slow.pl sub func_b 538498
27 func_slow.pl sub func_b 1337459
30 In total, 3 subroutines were called, one each of func_a(), func_b() and
34 on-CPU, func_b() spent 538.5 ms, and func_c() spent 799.0 ms. This exclusive
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
|
| H A D | sh_cputime_example.txt | 13 func_slow.sh func func_b 1
28 func_slow.sh func func_b 670372
35 func_slow.sh func func_b 1934839
41 on-CPU, func_b() spent 670.3 ms, and func_c() spent 1259 ms. This exclusive
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
|
| H A D | tcl_procflow_example.txt | 12 0 16073 3904972511039 -> func_b
15 0 16073 3904974531008 <- func_b
21 procedure and then shows that func_a began, and then called func_b.
|
| H A D | sh_cpudist_example.txt | 40 func_slow.sh, func, func_b
54 func_slow.sh, func, func_b
78 The inclusive function on-CPU times show that both func_b() and func_c()
81 functions called, and since func_a() called func_b() which called func_c(),
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Docs/Notes/ |
| H A D | ALLinclusive_notes.txt | 30 9 func_b()
41 20 func_b
46 func_a() calls func_b() which calls func_c(). Tracing the flow using
54 5 0 3052992111678 func_abc.sh 39 -> func_b
61 12 0 3052994131699 func_abc.sh 14 <- func_b
68 for both func_b() and func_c().
|
| H A D | ALLexclusive_notes.txt | 33 9 func_b()
44 20 func_b
49 func_a() calls func_b() which calls func_c(). Tracing the flow using
57 5 0 3052992111678 func_abc.sh 39 -> func_b
64 12 0 3052994131699 func_abc.sh 14 <- func_b
71 the time spent in both func_b() and func_c(). Or, you could say that
|
| H A D | ALLflow_notes.txt | 18 0 2963131870998 func_abc.pl -> func_b
21 0 2963133881166 func_abc.pl <- func_b
33 0 2963131870998 func_abc.pl -> func_b
35 0 2963133881166 func_abc.pl <- func_b
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Notes/ |
| H A D | ALLinclusive_notes.txt | 30 9 func_b()
41 20 func_b
46 func_a() calls func_b() which calls func_c(). Tracing the flow using
54 5 0 3052992111678 func_abc.sh 39 -> func_b
61 12 0 3052994131699 func_abc.sh 14 <- func_b
68 for both func_b() and func_c().
|
| H A D | ALLexclusive_notes.txt | 33 9 func_b()
44 20 func_b
49 func_a() calls func_b() which calls func_c(). Tracing the flow using
57 5 0 3052992111678 func_abc.sh 39 -> func_b
64 12 0 3052994131699 func_abc.sh 14 <- func_b
71 the time spent in both func_b() and func_c(). Or, you could say that
|
| H A D | ALLflow_notes.txt | 18 0 2963131870998 func_abc.pl -> func_b
21 0 2963133881166 func_abc.pl <- func_b
33 0 2963131870998 func_abc.pl -> func_b
35 0 2963133881166 func_abc.pl <- func_b
|