I am wondering how to export the statistics in the “Events View” (the first image) to a file or console for post-analysis.
I found a similar post in this forum, which mentions that modifying the scripts under the reports/ directory can get customized results. But it looks like that directory only contains CPU-side page-fault scripts, such as um_sum.py, um_total_sum.py, and um_cpu_page_faults_sum.py. Additionally, these scripts, along with the nsys stats --report command, seem to be specific to the “Stats System View” (see the second image).
So, how can I export the statistics from the “Events View” in the first image, including the description of each entry?
There isn’t a way to export the event view in specific, but all that data should be in the SQLite export file and might be in the JSON export, depending on what you’re looking for.
Are there specific classes/types of events you want to analyze?
Thank you very much for your help, @jkreibich! I just discovered that I can retrieve these data from the JSON export as you mentioned. I have a quick follow-up question, what’s the difference between the Events View and the Stats System View? I assume the former is for GPU-side statistics, and the latter is for host-side statistics. Is that right?
The Events View shows all the raw event data of the selected type. The Stats System View displays the results of the stats reports. This corresponds to the CLI command nsys stats. This is similar to how the Expert Systems View displays reports similar to the CLI command nsys analyze. In both cases, the reports are generated by Python modules that do various data manipulations to generate data views designed to offer insight into various aspects of application performance.
There are stats reports for various aspects of CPU/System performance, as well as GPU reports, and even reports that project fro CPU APIs to GPU kernels. The Stats and Expert Systems reports are also extensible. Since they are just Python modules, they’re easily modified/written by customers to suit their own specific needs. Modification and exploration is usually a little easier with the CLI interface, however.
