Invoke the Profiler Runtime Wrapper to Obtain Profiling Data
aocl profile [options] /path/to/executable [executable options]
- [options]are any additional flags you want to pass to the wrapper. Refer toaocl profile –helpfor a list of options and their uses.
- /path/to/executableis the path to the executable generated by the compiler.
- [executable options]are any options or arguments that need to be passed along to the executable.
Split the Execution and Data Post-Processing By default, the Profiler Runtime Wrapper automatically runs a post-processing step on your
- The--no-jsonflag only runs your executable and produces aprofile.monmonitor file without post-processing it.
- The--no-run <path to profile.mon file>flag does not invoke your executable and instead, just calls the post-processing step on the suppliedprofile.monfile.
Temporal Performance Collection
- You can control the rate at which the Profiler counters are sampled by setting the Profiler Runtime Wrapper's-periodflag. The specified period is the minimum number of kernel pipeline clock cycles between profiling samples. If you do not set a period, the default behavior is to profile as often as possible.For particularly large or long running designs, the amount of data generated by the default temporal period might result in a very largeprofile.monandprofile.jsonfiles. To reduce this file size, increase the sampling period or turn off temporal profiling.
- To turn off temporal profiling and instead collect performance data only once a kernel has finished executing, you can set the Profiler Runtime Wrapper's-no-temporalflag.If you collect the performance data only at the end of execution, the data is an average representation of the kernel's overall execution.