search

ROCm / rocprofiler

ROC profiler library. Profiling with perf-counters and derived metrics.
https://rocm.docs.amd.com/projects/rocprofiler/en/latest/
Other
116 stars 44 forks source link

rocprof behavior with both -d and -i options #44

Open yoann-heitz opened 3 years ago

yoann-heitz commented 3 years ago

When running rocprof command with -d option 

rocprof -d traces --hsa-trace my_script

The traces will be put in the following directory with the following architecture:

-traces
    -rpl_<date>_<time>_<id>
        -input_results_<date>_<time>
            -all the .txt traces

However when running the same command but with -i option 

rocprof -i input.xml -d traces --hsa-trace my_script

Then the traces will be put in the following directory with the following architecture:

-traces
    -all the .txt traces

In the first case, we can rerun rocprof several times without the risk of overwriting/having a collision with previous traces since other directories with unique ids (based on the time) are created in the given repository and the traces are put in those directories. In the second case, we risk to overwrite previous traces in the ./traces directory. Is it expected behavior?