Analysis Target Options
- Open theConfigure Analysiswindow.
- Choose a target type on theWHATpane and configure the options below.
To Do This
Inherit settings from Visual Studio* projectcheck box (supported for Visual Studio IDE only)
Enable/disable using the project currently opened in Visual Studio IDE and its current configuration settings as a target configuration. Checking this check box makes all other target configuration settings unavailable for editing.
Inherit system environment variablescheck box
Inherit and merge system and user-defined environment variables. Otherwise, only the user-defined variables are set.
Launch Application options:
Specify a full path to the application to analyze, which can be a binary file or script.
Specify input parameters for your application.
Use application directory as working directorycheck box
Automatically match your working and application directory (enabled by default). An
application directoryis the directory where your application resides. For example, for a Linux application
/home/foo/barthe application directory is
/home/foo. Application and working directories may be different if, for example, an application file is located in one directory but should be launched from a different directory (
Specify a directory to use for launching your analysis target. By default, this directory coincides with the application directory.
Attach to Process options:
Identify the executable to analyze by its name.
Identify the executable to analyze by its process ID (PID).
Selectbutton to see a list of currently available processes to attach to. As soon as you select a process of interest, the
VTuneautomatically populates the
Process namefields with the data for the selected process.
Launch Android Packageoptions:
Specify the name of the Android* package (
*.apk) to analyze.
To see Android applications and corresponding packages (
*.apk) currently installed on the device targeted for analysis, click the
Selectbutton. You may choose to view only debuggable APKs by selecting the corresponding checkbox.
For performance analysis on non-rooted devices, compile your Android application setting the debuggable attribute to true (
android:debuggable="true") but make sure to set
Application.mkto enable compilation with optimization.
Use MPI launchercheck box
Enable the check box to generate a command line configuration for MPI analysis. Configure the following MPI analysis options:
To Do This
User-defined environment variablesfield
Type or paste environment variables required for running your application.
Managed code profiling modemenu
Select a profiling mode for managed code.
Managedmode attributes data to managed source and only collects managed portion.
Nativemode collects everything but does not attribute data to managed source.
Mixedmode collects everything and attributes data to managed source where appropriate.
Automatically resume collection after (sec)
Specify the time that should elapse before the data collection is resumed. When this options is used, the collection starts in the paused mode automatically.
Automatically stop collection after (sec)
Set the duration of data collection in seconds starting from the target run. This is useful if you want to exclude some post-processing activities from the analysis results.
Analyze child processescheck box
Collect data on processes launched by the target process. Use this option when profiling an application with the script.
Selecting this option enables the
Per-process Configurationwhere you can specify child processes to analyze. For example, if your target application calls shell or makes processes, you can choose to exclude them from analysis and focus only on the processes you develop.
Defaultprocess configuration represents how all processes should be analyzed. This line cannot be removed, but can be customized. Depending on your choice, you may include/exclude from the data collection specific processes (
selfvalue) and the child processes they spawn (
This option is not applicable to hardware event-based analysis types.
Duration time estimatemenu
This option is deprecated. Use the
CPU sampling intervaloption on the
HOWconfiguration pane instead.
Estimate the application duration time. This value affects the size of collected data. For long running targets, sampling interval is increased to reduce the result size. For hardware event-based sampling analysis types, the
VTuneuses this estimate to apply a multiplier to the configured sample after value.
Allow multiple runscheck box
Enable multiple runs to achieve more precise results for hardware event-based collections. When disabled, the collector multiplexes events running a single collection, which lowers result precision.
Analyze system-widecheck box
Enable analyzing all processes running on the system. When disabled, only the target process is analyzed.
This option is applicable to hardware event-based sampling analysis types only.
Limit collected data bysection
If the amount of raw collected data is very large and takes long to process, use any of the following options to limit the collected data size:
The size of data stored in the result directory may not exactly match the specified result size due to the following reasons:
Specify CPU(s) to collect data on (for example: 2-8,10,12-14). This option is applicable to hardware event-based analysis types only.
Select finalization modesection
Finalization may take significant system resources. For a powerful target system, select
Fullmode to apply immediately after collection. Otherwise, shorten finalization with selecting the
fastmode (default) or defer it to run on another system (compute checksums only).
Provide a script that is launched on the target system before starting the collection. On the host system, you can prepare a custom script that prepares the target environment and calls the
VTunecollector in this environment.
An example of the wrapper script:
You can use the script to perform any actions available through the CLI of your target operating system, and use
"$*"to pass all arguments into the script and start
VTunecollection in this environment.
The following environment variables are available from the script:
Select where you want to store your result file. By default, the result is stored in the project directory.
Trace MPIcheck box (Linux* targets only)
Configure collectors to trace MPI code and determine MPI rank IDs in case of a non-Intel MPI library implementation.
Analyze KVM guest OScheck box (Linux targets only)
Enable KVM guest system profiling. For proper kernel symbol resolution, make sure to specify:
Analyze unplugged devicecheck box
Enable collection on an unplugged device to exclude ADB connection and power supply impact on the results. When this option is used, you configure and launch an analysis from the host but data collection starts after disconnecting the device from the USB cable or a network. Collection results are automatically transferred to the host as soon as you plug in the device back.
Select a system for result finalizationoptions
The result can be finalized on the same target system where the analysis is run (default). In this case make sure your target system is powerful enough for finalization. If you choose to finalize the result on another system,
VTunewill only compute module checksums to avoid an ambiguity in resolving binaries on a different system.
- System-wide profiling is not supported for the user-mode sampling and tracing collection.
- For driverless event-based sampling data collection,VTunesupports local and remote Launch Application, Attach to Process and Profile System target types but their support fully depends on the Linux Perf profiling credentials specified in theProfiler/proc/sys/kernel/perf_event_paranoidfile and managed by the administrator of your system using root credentials. For more information, see theperf_event related configuration filestopic at http://man7.org/linux/man-pages/man2/perf_event_open.2.html. By default, only user processes profiling at the both user and kernel spaces is permitted, so you need granting wider profiling credentials via theperf_event_paranoidfile to employ the Profile System target type.