|
| 1 | +Display help when called without subcommands |
| 2 | + |
| 3 | + $ olly --help=plain |
| 4 | + NAME |
| 5 | + olly - An observability tool for OCaml programs |
| 6 | + |
| 7 | + SYNOPSIS |
| 8 | + olly COMMAND … |
| 9 | + |
| 10 | + COMMANDS |
| 11 | + gc-stats [OPTION]… [EXECUTABLE]… |
| 12 | + Report the GC latency profile and stats. |
| 13 | + |
| 14 | + help [--man-format=FMT] [OPTION]… [TOPIC] |
| 15 | + Display help about olly and olly commands. |
| 16 | + |
| 17 | + trace [OPTION]… TRACEFILE [EXECUTABLE]… |
| 18 | + Save the runtime trace to file. |
| 19 | + |
| 20 | + COMMON OPTIONS |
| 21 | + --help[=FMT] (default=auto) |
| 22 | + Show this help in format FMT. The value FMT must be one of auto, |
| 23 | + pager, groff or plain. With auto, the format is pager or plain |
| 24 | + whenever the TERM env var is dumb or undefined. |
| 25 | + |
| 26 | + EXIT STATUS |
| 27 | + olly exits with: |
| 28 | + |
| 29 | + 0 on success. |
| 30 | + |
| 31 | + 123 on indiscriminate errors reported on standard error. |
| 32 | + |
| 33 | + 124 on command line parsing errors. |
| 34 | + |
| 35 | + 125 on unexpected internal errors (bugs). |
| 36 | + |
| 37 | +Display help for trace |
| 38 | + |
| 39 | + $ olly trace --help=plain |
| 40 | + NAME |
| 41 | + olly-trace - Save the runtime trace to file. |
| 42 | + |
| 43 | + SYNOPSIS |
| 44 | + olly trace [OPTION]… TRACEFILE [EXECUTABLE]… |
| 45 | + |
| 46 | + DESCRIPTION |
| 47 | + Save the runtime trace to file. |
| 48 | + |
| 49 | + ARGUMENTS |
| 50 | + EXECUTABLE |
| 51 | + Executable and arguments to trace. |
| 52 | + |
| 53 | + TRACEFILE (required) |
| 54 | + Target trace file name. |
| 55 | + |
| 56 | + OPTIONS |
| 57 | + -a [directory:]pid, --attach=[directory:]pid |
| 58 | + Attach to the process with the given PID. The directory containing |
| 59 | + the PID.events file may be specified. This option cannot be |
| 60 | + combined with EXECUTABLE. |
| 61 | + |
| 62 | + -c, --emit-counters |
| 63 | + Emit runtime counter events. |
| 64 | + |
| 65 | + -d dir, --dir=dir |
| 66 | + Sets the directory where the .events files containing the runtime |
| 67 | + event tracing system’s ring buffers will be located. If not |
| 68 | + specified a temporary directory will be used. |
| 69 | + |
| 70 | + -f format, --format=format (absent=fuchsia) |
| 71 | + Format of the target trace, options are: "fuchsia" (Perfetto), |
| 72 | + "json" (Chrome Trace Format). |
| 73 | + |
| 74 | + --freq=freq (absent=0.1) |
| 75 | + Set the interval that olly sleeps in seconds, after performing a |
| 76 | + [Runtime_events.read_poll]. Fractions of seconds are supported. A |
| 77 | + value of 0.0 will skip sleeping altogether. |
| 78 | + |
| 79 | + --log-wsize=log-wsize |
| 80 | + Size of the per-domain runtime events ring buffers in log powers |
| 81 | + of two words. Defaults to 16. |
| 82 | + |
| 83 | + COMMON OPTIONS |
| 84 | + These options are common to all commands. |
| 85 | + |
| 86 | + --help[=FMT] (default=auto) |
| 87 | + Show this help in format FMT. The value FMT must be one of auto, |
| 88 | + pager, groff or plain. With auto, the format is pager or plain |
| 89 | + whenever the TERM env var is dumb or undefined. |
| 90 | + |
| 91 | + MORE HELP |
| 92 | + Use olly COMMAND --help for help on a single command. |
| 93 | + EXIT STATUS |
| 94 | + olly trace exits with: |
| 95 | + |
| 96 | + 0 on success. |
| 97 | + |
| 98 | + 123 on indiscriminate errors reported on standard error. |
| 99 | + |
| 100 | + 124 on command line parsing errors. |
| 101 | + |
| 102 | + 125 on unexpected internal errors (bugs). |
| 103 | + |
| 104 | + BUGS |
| 105 | + Check bug reports at |
| 106 | + http://github.com/tarides/runtime_events_tools/issues. |
| 107 | + |
| 108 | + SEE ALSO |
| 109 | + olly(1) |
| 110 | + |
| 111 | + |
| 112 | +Display help for gc-stats |
| 113 | + |
| 114 | + $ olly gc-stats --help=plain |
| 115 | + NAME |
| 116 | + olly-gc-stats - Report the GC latency profile and stats. |
| 117 | + |
| 118 | + SYNOPSIS |
| 119 | + olly gc-stats [OPTION]… [EXECUTABLE]… |
| 120 | + |
| 121 | + DESCRIPTION |
| 122 | + Report the GC latency profile. |
| 123 | + |
| 124 | + Wall time |
| 125 | + Real execution time of the program |
| 126 | + |
| 127 | + CPU time |
| 128 | + Total CPU time across all domains |
| 129 | + |
| 130 | + GC time |
| 131 | + Total time spent by the program performing garbage collection |
| 132 | + (major and minor) |
| 133 | + |
| 134 | + GC overhead |
| 135 | + Percentage of time taken up by GC against the total execution time |
| 136 | + |
| 137 | + GC time per domain |
| 138 | + Time spent by every domain performing garbage collection (major |
| 139 | + and minor cycles). Domains are reported with their domain ID (e.g. |
| 140 | + `Domain 0`) |
| 141 | + |
| 142 | + GC latency profile |
| 143 | + Mean, standard deviation and percentile latency profile of GC |
| 144 | + events. |
| 145 | + |
| 146 | + GC allocations |
| 147 | + GC allocation and promotion in machine words during program |
| 148 | + execution. Counts of Compactions, and Minor and Major collections. |
| 149 | + |
| 150 | + ARGUMENTS |
| 151 | + EXECUTABLE |
| 152 | + Executable and arguments to trace. |
| 153 | + |
| 154 | + OPTIONS |
| 155 | + -a [directory:]pid, --attach=[directory:]pid |
| 156 | + Attach to the process with the given PID. The directory containing |
| 157 | + the PID.events file may be specified. This option cannot be |
| 158 | + combined with EXECUTABLE. |
| 159 | + |
| 160 | + -d dir, --dir=dir |
| 161 | + Sets the directory where the .events files containing the runtime |
| 162 | + event tracing system’s ring buffers will be located. If not |
| 163 | + specified a temporary directory will be used. |
| 164 | + |
| 165 | + --freq=freq (absent=0.1) |
| 166 | + Set the interval that olly sleeps in seconds, after performing a |
| 167 | + [Runtime_events.read_poll]. Fractions of seconds are supported. A |
| 168 | + value of 0.0 will skip sleeping altogether. |
| 169 | + |
| 170 | + --json |
| 171 | + Print the output in json instead of human-readable format. |
| 172 | + |
| 173 | + --log-wsize=log-wsize |
| 174 | + Size of the per-domain runtime events ring buffers in log powers |
| 175 | + of two words. Defaults to 16. |
| 176 | + |
| 177 | + -o output, --output=output |
| 178 | + Redirect the output of `olly` to specified file. The output of the |
| 179 | + command is not redirected. |
| 180 | + |
| 181 | + COMMON OPTIONS |
| 182 | + These options are common to all commands. |
| 183 | + |
| 184 | + --help[=FMT] (default=auto) |
| 185 | + Show this help in format FMT. The value FMT must be one of auto, |
| 186 | + pager, groff or plain. With auto, the format is pager or plain |
| 187 | + whenever the TERM env var is dumb or undefined. |
| 188 | + |
| 189 | + MORE HELP |
| 190 | + Use olly COMMAND --help for help on a single command. |
| 191 | + EXIT STATUS |
| 192 | + olly gc-stats exits with: |
| 193 | + |
| 194 | + 0 on success. |
| 195 | + |
| 196 | + 123 on indiscriminate errors reported on standard error. |
| 197 | + |
| 198 | + 124 on command line parsing errors. |
| 199 | + |
| 200 | + 125 on unexpected internal errors (bugs). |
| 201 | + |
| 202 | + BUGS |
| 203 | + Check bug reports at |
| 204 | + http://github.com/tarides/runtime_events_tools/issues. |
| 205 | + |
| 206 | + SEE ALSO |
| 207 | + olly(1) |
| 208 | + |
0 commit comments