Intel® VTune™ Amplifier XE and Intel® VTune™ Amplifier for Systems Help

Viewing Data Collected Remotely

Opening a result collected by the Intel® VTune™ Amplifier on a remote system depends on the mode used to start the data collection.

If Data Collection Is Started From:

Do This:

VTune Amplifier GUI on the host system

No action is required. VTune Amplifier opens the collection result automatically when your analysis is complete.

VTune Amplifier CLI on the host system

Open the collected result (*.amplxe) in GUI. VTune Amplifier sorts and filters the data and presents it to maximize intelligent inferences on the performance problem.

Target remote system (for example, applicable to SEP collection, Perf* collection, Energy Analysis collection via Intel SoC Watch command line collector)

Depending on your collection type, use any of the following options to view your results in the VTune Amplifier GUI:

  • Open the *.amplxe result directly: This method is easiest but does not allow specifying symbols after analysis and re-finalizing the result (operating system limitation). If you need to update the search list for binary and source files, specify the required paths using the --search-dir/--source-search-dir options from CLI or by using the Source Search and Binary/Symbol Search dialog boxes in GUI and re-run the collection.

  • Import a data file collected directly on the target system

  • Import raw data: This method requires you to:

    • Import the results/data.0 directory created by amplxe-cl into a new or existing project.

    • If required, specify the location of binaries/symbols on the host system to see function names, assembly, or source.

    • Re-resolve the result.

Note

  • Remote analysis on Android*, Windows* and embedded Linux* systems is supported in the Intel® VTune™ Amplifier for Systems, part of the Intel® System Studio. VTune Amplifier XE supports remote data collection from GUI on regular Linux systems.

  • For performance analysis on an Android* system, Java* functions data representation (assembly, source, and/or DEX Byte Code) depend on your installation settings specified in local.prop.

See Also