Import Results and Traces into
VTune
Profiler GUI
VTune
GUI Profiler
If you collect performance data either remotely with the
Intel® VTune™
command line interface or with standalone collectors (such as SEP collector, Intel SoC Watch collector, or Linux* Perf* collector), import this data (result or trace) to the
Profiler
VTune
project to analyze it in the graphical interface.
Profiler
To get ready for the import:
- Create aVTuneproject for the data to be imported.Profiler
- In theConfigure Analysiswindow, click theSearch Sources/Binariesbutton at the bottom to specify search directories for the data to be imported. When you open the Source/Assembly view for the collected data, theVTuneautomatically applies binary/source search paths for proper symbol resolution.ProfilerMake sure the search directories are accessible to theVTune. For example, if you are to import the data collected remotely, you need to copy the sources and binaries to the host system where theProfilerVTuneis installed or make them available via a shared drive.Profiler
- Select theImportoption using any of the following options:
- From Microsoft Visual Studio* IDE: Open a project where you want to locate the imported result and go toTools>.Intel® VTune™Profilerversion> Import Result...
- From standaloneVTuneinterface: Open a project where you want to locate the imported result, click theProfiler
menu button and select
Import Result..., or click theImport Resultbutton on the toolbar.
TheImportwindow opens. - Choose between two options:
- import an*.result (a marker file with associated result directories) collected remotely with thevtuneVTunecommand line interface;Profiler
- import a raw trace file collected by standalone collector tools.
Import Results
You can perform multiple collections on a remote system (with or without result finalization) with a full-fledged
VTune
command line interface, copy the result directories to the host, and import the result(s) into a
Profiler
VTune
project.
Profiler
To import result directories into a
VTune
project: Profiler
- In theImportwindow, select theImport a result into the current projectoption.
- Click the
browse button to navigate to the required directory.
- If required, click theSearch Sources/Binariesbutton on the right to view/modify the search directories.
- Click theImportbutton on the right.VTunecopies the result directory to the current project folder and result name appears in the Project Navigator as a node of the current project.Profiler
If you do not need to copy a result, select the
Import via a link instead of a result copy
option.
VTune
will import the result via this link.
Profiler
Import Raw Trace Data
You can also import performance trace files collected using:
- SEP Collector
- SoC Watch Collector
- Perf Collector
VTune
GUI.
Profiler
You can import these data formats:
- *.tb6/*.tb7(sampling raw data files collected with the low-level SEP collector)
- *.perf(Linux* Perf data files)
- *.csv(external data collection files in the predefined format)
- *.pwr(processed Intel SoC Watch files with energy analysis data)
- *.json(FPGA performance data collected with the Profiler Runtime Wrapper)For FPGA data collected with the Profiler Runtime Wrapper, you must import a folder with theprofile.jsonfile. Use theImport multiple trace files from a directoryoption in theImportwindow. See the section below on importing trace files into aVTuneproject.Profiler
Prerequisites for importing a
*.perf
file with event-based sampling data:
Run the Perf collection with the predefined command line options:
- For application analysis:perf record -o <trace_file_name>.perf --call-graph dwarf -e cpu-cycles,instructions <application_to_launch>
- For process analysis:perf record -o <trace_file_name>.perf --call-graph dwarf -e cpu-cycles,instructions <application_to_launch> -p <PID> sleep 15
where the
-e
option is used to specify a list of events to collect as
-e <
;
list of events
>--call-graph
option (optional) configures samples to be collected together with the thread call stack at the moment a sample is taken. See Linux Perf documentation on possible call stack collection options (for example,
dwarf
) and its availability in different OS kernel versions.
The Linux kernel exposes Perf API to the Perf tool starting from version 2.6.31. Any attempts to run the Perf tool on kernels prior to this version lead to undefined results or even crashes. See Linux Perf documentation for more details.
To import trace files into a
VTune
project: Profiler
- In theImportwindow, select theImport raw trace dataoption.
- Click the
browse button to navigate to the required file.
To import multiple files, select theImport multiple trace files from a directoryoption.For FPGA data collected with the Profiler Runtime Wrapper, you need to use this option to import afolderwith theprofile.jsonfile. See the FPGA Optimization Guide for Intel® oneAPI Toolkits for details on generating the profiling data. - If required, click theSearch Sources/Binariesbutton on the right to view/modify the search directories.
- Click theImportbutton on the right.VTunecopies the trace file (or a directory with multiple traces) to the project directory, creates anProfiler*.result directory, finalizes the trace(s) in the directory, and imports it to the current project. When you open the result in thevtuneVTune, it uses all applicable viewpoints to represent the data.Profiler
- To reduce the size of the imported data, consider removing the copy of the trace file in the project directory using theRemove raw collector data after resolving the resultoption available fromOptions... >tab in the standalone interface menuIntel VTuneProfilerversion> General
or from
Tools > Options... >tab in Microsoft Visual Studio* IDE. This option makes the result smaller but prevents future re-finalization.Intel VTuneProfilerversion> General - You can run a custom data collection (with a third-party collector or your own collection utility) in parallel with theVTuneanalysis run, convert the collected data to aProfiler*.csvfile and import the this file to theVTuneproject using the Import from CSV GUI option orProfiler-importCLI option. You may also choose to use the Custom collector option of theVTuneto run your custom collection directly from theProfilerVTune.Profiler