| /netbsd-src/external/cddl/dtracetoolkit/dist/Docs/Examples/ |
| H A D | j_profile_example.txt | 26 Func_loop.func_c()V
38 Func_loop.func_c()V
50 Func_loop.func_c()V
62 Func_loop.func_c()V
74 Func_loop.func_c()V
86 Func_loop.func_c()V
98 Func_loop.func_c()V
111 The most frequent stacks had Func_loop.func_c() on CPU, with a stack trace
125 Func_loop.func_c()V
137 Func_loop.func_c()V
[all …]
|
| H A D | php_cputime_example.txt | 14 func_abc.php func func_c 1
20 func_abc.php func func_c 17
28 func_abc.php func func_c 39
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
41 The inclusive subroutine on-CPU times show that func_c() spent around 39
45 func_b() which called func_c(), these times make perfect sense.
|
| H A D | php_syscolors_example.txt | 26 [2;35m0 18426/1 43 func_abc.php:12 func -> func_c[0m
31 [2;35m0 18426/1 34 func_abc.php:6 func <- func_c[0m
53 [2;35m0 18426/1 43 func_abc.php:12 func -> func_c[0m
58 [2;35m0 18426/1 34 func_abc.php:6 func <- func_c[0m
60 we can see that we are at Line 12 of the program which invokes func_c. func_c
62 second later nanosleep returns, then sleep finishes, then func_c finishes.
|
| H A D | py_profile_example.txt | 17 [ ./func_slow.py:3 (func_c) ]
33 [ ./func_slow.py:3 (func_c) ]
123 [ ./func_slow.py:3 (func_c) ]
139 [ ./func_slow.py:3 (func_c) ]
155 [ ./func_slow.py:3 (func_c) ]
186 [ ./func_slow.py:3 (func_c) ]
202 [ ./func_slow.py:3 (func_c) ]
218 [ ./func_slow.py:3 (func_c) ]
234 [ ./func_slow.py:3 (func_c) ]
273 [ ./func_slow.py:3 (func_c) ]
[all …]
|
| H A D | php_calldist_example.txt | 24 func_abc.php, func, func_c
38 func_abc.php, func, func_c
63 func_c(), and sleep was called 3 times. You can see this reflected in the
70 The inclusive subroutine elapsed times show that func_c() took between 0.5
74 func_b() which called func_c(), these times make sense.
|
| H A D | tcl_cputime_example.txt | 32 16038 proc func_c 1619323
41 16038 proc func_c 1619360
42 16038 cmd func_c 1619404
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 | 24 func_abc.php, func, func_c
38 func_abc.php, func, func_c
63 func_c(), and sleep was called 3 times. You can see this reflected in the
70 The inclusive subroutine elapsed times show that func_c() took between 32
75 func_a() called func_b() which called func_c(), these times make sense.
|
| H A D | pl_cputime_example.txt | 14 func_slow.pl sub func_c 1
21 func_slow.pl sub func_c 798961
26 func_slow.pl sub func_c 798961
31 func_c().
34 on-CPU, func_b() spent 538.5 ms, and func_c() spent 799.0 ms. This exclusive
37 The inclusive subroutine on-CPU times show that func_c() spent around 799.0 ms
40 called, and since func_a() called func_b() which called func_c(), these
|
| H A D | sh_cputime_example.txt | 14 func_slow.sh func func_c 1
29 func_slow.sh func func_c 1259073
34 func_slow.sh func func_c 1262209
41 on-CPU, func_b() spent 670.3 ms, and func_c() spent 1259 ms. This exclusive
44 The inclusive function on-CPU times show that func_c() spent around 1.3
47 called, and since func_a() called func_b() which called func_c(), these
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Examples/ |
| H A D | j_profile_example.txt | 26 Func_loop.func_c()V
38 Func_loop.func_c()V
50 Func_loop.func_c()V
62 Func_loop.func_c()V
74 Func_loop.func_c()V
86 Func_loop.func_c()V
98 Func_loop.func_c()V
111 The most frequent stacks had Func_loop.func_c() on CPU, with a stack trace
125 Func_loop.func_c()V
137 Func_loop.func_c()V
[all …]
|
| H A D | php_cputime_example.txt | 14 func_abc.php func func_c 1
20 func_abc.php func func_c 17
28 func_abc.php func func_c 39
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
41 The inclusive subroutine on-CPU times show that func_c() spent around 39
45 func_b() which called func_c(), these times make perfect sense.
|
| H A D | php_syscolors_example.txt | 26 [2;35m0 18426/1 43 func_abc.php:12 func -> func_c[0m
31 [2;35m0 18426/1 34 func_abc.php:6 func <- func_c[0m
53 [2;35m0 18426/1 43 func_abc.php:12 func -> func_c[0m
58 [2;35m0 18426/1 34 func_abc.php:6 func <- func_c[0m
60 we can see that we are at Line 12 of the program which invokes func_c. func_c
62 second later nanosleep returns, then sleep finishes, then func_c finishes.
|
| H A D | py_profile_example.txt | 17 [ ./func_slow.py:3 (func_c) ]
33 [ ./func_slow.py:3 (func_c) ]
123 [ ./func_slow.py:3 (func_c) ]
139 [ ./func_slow.py:3 (func_c) ]
155 [ ./func_slow.py:3 (func_c) ]
186 [ ./func_slow.py:3 (func_c) ]
202 [ ./func_slow.py:3 (func_c) ]
218 [ ./func_slow.py:3 (func_c) ]
234 [ ./func_slow.py:3 (func_c) ]
273 [ ./func_slow.py:3 (func_c) ]
[all …]
|
| H A D | php_calldist_example.txt | 24 func_abc.php, func, func_c
38 func_abc.php, func, func_c
63 func_c(), and sleep was called 3 times. You can see this reflected in the
70 The inclusive subroutine elapsed times show that func_c() took between 0.5
74 func_b() which called func_c(), these times make sense.
|
| H A D | tcl_cputime_example.txt | 32 16038 proc func_c 1619323
41 16038 proc func_c 1619360
42 16038 cmd func_c 1619404
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 | 24 func_abc.php, func, func_c
38 func_abc.php, func, func_c
63 func_c(), and sleep was called 3 times. You can see this reflected in the
70 The inclusive subroutine elapsed times show that func_c() took between 32
75 func_a() called func_b() which called func_c(), these times make sense.
|
| H A D | pl_cputime_example.txt | 14 func_slow.pl sub func_c 1
21 func_slow.pl sub func_c 798961
26 func_slow.pl sub func_c 798961
31 func_c().
34 on-CPU, func_b() spent 538.5 ms, and func_c() spent 799.0 ms. This exclusive
37 The inclusive subroutine on-CPU times show that func_c() spent around 799.0 ms
40 called, and since func_a() called func_b() which called func_c(), these
|
| H A D | sh_cputime_example.txt | 14 func_slow.sh func func_c 1
29 func_slow.sh func func_c 1259073
34 func_slow.sh func func_c 1262209
41 on-CPU, func_b() spent 670.3 ms, and func_c() spent 1259 ms. This exclusive
44 The inclusive function on-CPU times show that func_c() spent around 1.3
47 called, and since func_a() called func_b() which called func_c(), these
|
| H A D | sh_cpudist_example.txt | 46 func_slow.sh, func, func_c
60 func_slow.sh, func, func_c
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 | 24 3 func_c()
34 13 func_c
46 func_a() calls func_b() which calls func_c(). Tracing the flow using
57 8 0 3052993121693 func_abc.sh 60 -> func_c
60 11 0 3052994131685 func_abc.sh 50 <- func_c
68 for both func_b() and func_c().
|
| H A D | ALLexclusive_notes.txt | 27 3 func_c()
37 13 func_c
49 func_a() calls func_b() which calls func_c(). Tracing the flow using
60 8 0 3052993121693 func_abc.sh 60 -> func_c
63 11 0 3052994131685 func_abc.sh 50 <- func_c
71 the time spent in both func_b() and func_c(). Or, you could say that
|
| H A D | ALLflow_notes.txt | 19 0 2963132871121 func_abc.pl -> func_c
20 0 2963133881150 func_abc.pl <- func_c
34 0 2963132871121 func_abc.pl -> func_c
37 1 2963133881150 func_abc.pl <- func_c
|
| /netbsd-src/external/cddl/dtracetoolkit/dist/Notes/ |
| H A D | ALLinclusive_notes.txt | 24 3 func_c()
34 13 func_c
46 func_a() calls func_b() which calls func_c(). Tracing the flow using
57 8 0 3052993121693 func_abc.sh 60 -> func_c
60 11 0 3052994131685 func_abc.sh 50 <- func_c
68 for both func_b() and func_c().
|
| H A D | ALLexclusive_notes.txt | 27 3 func_c()
37 13 func_c
49 func_a() calls func_b() which calls func_c(). Tracing the flow using
60 8 0 3052993121693 func_abc.sh 60 -> func_c
63 11 0 3052994131685 func_abc.sh 50 <- func_c
71 the time spent in both func_b() and func_c(). Or, you could say that
|
| H A D | ALLflow_notes.txt | 19 0 2963132871121 func_abc.pl -> func_c
20 0 2963133881150 func_abc.pl <- func_c
34 0 2963132871121 func_abc.pl -> func_c
37 1 2963133881150 func_abc.pl <- func_c
|