2022-05-08 07:57:09 -05:00
# Omnitrace: Application Profiling, Tracing, and Analysis
2021-08-25 11:39:00 -05:00
2022-04-04 15:27:38 -05:00
[](https://github.com/AMDResearch/omnitrace/actions/workflows/ubuntu-bionic.yml)
[](https://github.com/AMDResearch/omnitrace/actions/workflows/ubuntu-focal-external.yml)
[](https://github.com/AMDResearch/omnitrace/actions/workflows/ubuntu-focal.yml)
[](https://github.com/AMDResearch/omnitrace/actions/workflows/ubuntu-focal-external-rocm.yml)
2022-05-08 07:57:09 -05:00
> ***[Omnitrace](https://github.com/AMDResearch/omnitrace) is an AMD open source research project and is not supported as part of the ROCm software stack.***
2022-04-05 20:40:27 -05:00
2022-05-08 07:57:09 -05:00
## Documentation
2021-09-02 13:14:58 -05:00
2022-05-08 07:57:09 -05:00
The full documentation for [omnitrace ](https://github.com/AMDResearch/omnitrace ) is available at [amdresearch.github.io/omnitrace ](https://amdresearch.github.io/omnitrace/ ).
## Quick Start
### Omnitrace Settings
`omnitrace-avail -Sd` will provide a list of all the possible omnitrace settings, their current value, and a description of the setting
when running an instrumented binary.
### Omnitrace Executable
The `omnitrace` executable is used to instrument an existing binary.
2021-09-02 13:14:58 -05:00
2021-09-06 22:23:24 -05:00
```shell
2021-11-24 04:59:59 -06:00
omnitrace --help
omnitrace <omnitrace-options> -- <exe-or-library> <exe-options>
2021-08-25 11:39:00 -05:00
```
2021-09-02 13:14:58 -05:00
#### Binary Rewrite
2021-08-25 11:39:00 -05:00
2021-09-06 22:23:24 -05:00
Rewrite the text section of an executable or library with instrumentation:
2021-08-25 11:39:00 -05:00
2021-09-06 22:23:24 -05:00
```shell
2021-11-24 04:59:59 -06:00
omnitrace -o app.inst -- /path/to/app
2021-08-25 11:39:00 -05:00
```
2021-09-02 13:14:58 -05:00
In binary rewrite mode, if you also want instrumentation in the linked libraries, you must also rewrite those libraries.
Example of rewriting the functions starting with `"hip"` with instrumentation in the amdhip64 library:
2021-09-06 22:23:24 -05:00
```shell
2021-09-02 13:14:58 -05:00
mkdir -p ./lib
2021-11-24 04:59:59 -06:00
omnitrace -R '^hip' -o ./lib/libamdhip64.so.4 -- /opt/rocm/lib/libamdhip64.so.4
2021-09-02 13:14:58 -05:00
export LD_LIBRARY_PATH = ${ PWD } /lib:${ LD_LIBRARY_PATH }
2021-08-25 11:39:00 -05:00
```
2021-09-02 13:14:58 -05:00
2022-04-05 20:40:27 -05:00
> ***Verify via `ldd` that your executable will load the instrumented library -- if you built your executable with***
> ***an RPATH to the original library's directory, then prefixing `LD_LIBRARY_PATH` will have no effect.***
2021-09-02 13:14:58 -05:00
Once you have rewritten your executable and/or libraries with instrumentation, you can just run the (instrumented) executable
or exectuable which loads the instrumented libraries normally, e.g.:
2021-09-06 22:23:24 -05:00
```shell
./app.inst
```
2021-11-24 04:59:59 -06:00
If you want to re-define certain settings to new default in a binary rewrite, use the `--env` option. This `omnitrace` option
2022-05-10 17:30:45 -05:00
will set the environment variable to the given value but will not override it. E.g. the default value of `OMNITRACE_PERFETTO_BUFFER_SIZE_KB`
2021-09-06 22:23:24 -05:00
is 1024000 KB (1 GiB):
```shell
# buffer size defaults to 1024000
2021-11-24 04:59:59 -06:00
omnitrace -o app.inst -- /path/to/app
2021-09-06 22:23:24 -05:00
./app.inst
```
2022-05-10 17:30:45 -05:00
Passing `--env OMNITRACE_PERFETTO_BUFFER_SIZE_KB=5120000` will change the default value in `app.inst` to 5120000 KiB (5 GiB):
2021-09-06 22:23:24 -05:00
```shell
# defaults to 5 GiB buffer size
2022-05-10 17:30:45 -05:00
omnitrace -o app.inst --env OMNITRACE_PERFETTO_BUFFER_SIZE_KB = 5120000 -- /path/to/app
2021-09-06 22:23:24 -05:00
./app.inst
```
```shell
# override default 5 GiB buffer size to 200 MB
2022-05-10 17:30:45 -05:00
export OMNITRACE_PERFETTO_BUFFER_SIZE_KB = 200000
2021-09-02 13:14:58 -05:00
./app.inst
2021-08-25 11:39:00 -05:00
```
2021-09-02 13:14:58 -05:00
#### Runtime Instrumentation
2021-08-25 11:39:00 -05:00
2021-09-02 13:14:58 -05:00
Runtime instrumentation will not only instrument the text section of the executable but also the text sections of the
2022-05-08 07:57:09 -05:00
linked libraries. Thus, it may be useful to exclude those libraries via the `-ME` (module exclude) regex option
or exclude specific functions with the `-E` regex option.
2021-09-02 13:14:58 -05:00
2021-09-06 22:23:24 -05:00
```shell
2021-11-24 04:59:59 -06:00
omnitrace -- /path/to/app
omnitrace -ME '^(libhsa-runtime64|libz\\.so)' -- /path/to/app
omnitrace -E 'rocr::atomic|rocr::core|rocr::HSA' -- /path/to/app
2021-08-25 11:39:00 -05:00
```
2022-05-08 07:57:09 -05:00
### Visualizing Perfetto Results
Visit [ui.perfetto.dev ](https://ui.perfetto.dev ) in your browser and open up the `.proto` file(s) created by omnitrace.




2021-09-02 13:14:58 -05:00
2021-11-24 04:59:59 -06:00
## Merging the traces from rocprof and omnitrace
2021-09-02 13:14:58 -05:00
2022-01-26 23:25:00 -06:00
This section requires installing [Julia ](https://julialang.org/ ).
### Installing Julia
Julia is available via Linux package managers or may be available via a module. Debian-based distributions such as Ubuntu can run (as a super-user):
```shell
apt-get install julia
```
Once Julia is installed, install the necessary packages (this operation only needs to be performed once):
```shell
julia -e 'using Pkg; for name in ["JSON", "DataFrames", "Dates", "CSV", "Chain", "PrettyTables"]; Pkg.add(name); end'
```
2022-04-05 20:40:27 -05:00
> ***Using `rocprof` externally for tracing is deprecated. The current version has built-in support for***
> ***recording the GPU activity and HIP API calls. If you want to use an external rocprof, either***
> ***configure CMake with `-DOMNITRACE_USE_ROCTRACER=OFF` or explicitly set `OMNITRACE_ROCTRACER_ENABLED=OFF` in the***
> ***environment.***
2021-09-06 22:23:24 -05:00
2021-11-24 04:59:59 -06:00
Use the `omnitrace-merge.jl` Julia script to merge rocprof and perfetto traces.
2021-09-02 13:14:58 -05:00
2021-09-06 22:23:24 -05:00
```shell
2022-05-08 07:57:09 -05:00
export OMNITRACE_USE_ROCTRACER = OFF
2021-09-06 22:23:24 -05:00
rocprof --hip-trace --roctx-trace --stats ./app.inst
2021-11-24 04:59:59 -06:00
omnitrace-merge.jl results.json omnitrace-app.inst-output/2021-09-02_01.03_PM/*.proto
2021-08-25 11:39:00 -05:00
```
2021-09-02 13:14:58 -05:00
## Use Perfetto tracing with System Backend
2022-05-30 18:25:12 -05:00
Enable `traced` and `perfetto` in the background:
2021-09-02 13:14:58 -05:00
2021-09-06 22:23:24 -05:00
```shell
2021-09-02 13:14:58 -05:00
pkill traced
traced --background
2022-05-30 18:25:12 -05:00
perfetto --out ./omnitrace-perfetto.proto --txt -c ${ OMNITRACE_ROOT } /share/omnitrace.cfg --background
2021-08-25 11:39:00 -05:00
```
2021-09-02 13:14:58 -05:00
2022-05-30 18:25:12 -05:00
Configure omnitrace to use the perfetto system backend:
2021-09-02 13:14:58 -05:00
2021-09-06 22:23:24 -05:00
```shell
2022-05-10 17:30:45 -05:00
export OMNITRACE_PERFETTO_BACKEND = system
2021-08-25 11:39:00 -05:00
```
2022-05-30 18:25:12 -05:00
And finally, execute your instrumented application. Either the binary rewritten application:
2021-09-02 13:14:58 -05:00
2021-09-06 22:23:24 -05:00
```shell
2022-05-30 18:25:12 -05:00
omnitrace -o ./myapp.inst -- ./myapp
./myapp.inst
```
Or with runtime instrumentation:
```shell
omnitrace -- ./myapp
2021-08-25 11:39:00 -05:00
```