Pane: Attach to Process

The Attach to Process pane helps you specify a specific process to attach to and analyze with the Intel® VTune™ Amplifier .

To access this pane:

  1. On the Intel® VTune™ Amplifier toolbar, click the Project Properties button to open the Project Properties dialog box.

    The Target tab opens by default.

  2. Select the Attach to Process entry from the Target Type drop-down menu.

  3. For a remote collection on an embedded Linux* or Android* system, use the Target system drop-down menu to specify a system used for analysis.

    Note

    Remote analysis on Android* and Linux* embedded systems is supported in the Intel® VTune™ Amplifier 2014 for Systems, part of the Intel® System Studio.

Use this pane to choose and configure a process to analyze.

Use This

To Do This

Inherit settings from Visual Studio* project check box (supported for Visual Studio IDE only)

Enable/disable using the project currently opened in Visual Studio* and its current configuration settings as a target configuration. Checking this check box makes all other target configuration settings unavailable for editing.

Process name

Identify the executable to analyze by its name.

PID

Identify the executable to analyze by its process ID (PID).

Browse button

Open the Select Process dialog box that provides a list of currently available processes to attach to. This button shows up if you selected a remote Linux or Android target. As soon as you select a process of interest in the Select Process dialog box and click OK, the VTune Amplifier automatically populates the Process name and PID fields with the data for the selected process.

Managed code profiling mode menu

Select a profiling mode for managed code. Managed mode attributes data to managed source and only collects managed portion. Native mode collects everything but does not attribute data to managed source. Mixed mode collects everything and attributes data to managed source where appropriate.

Note

Attaching to managed runtime processes is supported only for user-mode sampling and tracing analysis types.

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.

Use the Advanced section to provide more details on your target configuration.

Use This

To Do This

Analyze child processes check box

Collect data on processes launched by the target process. Use this option when profiling an application with the script.

Per-process configuration field

Click the Modify button to open the Per-process Configuration dialog box and 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.

This option is not applicable to hardware event-based analysis types.

Duration time estimate menu

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 VTune Amplifier uses this estimate to apply a multiplier to the configured sample after value.

Allow multiple runs check 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-wide check 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.

Collection data limit spin box

Limit the amount of the raw data to be collected. Use this option to start analyzing the beginning of the target execution when the amount of collected data is very large and takes long to process.

Outcome: VTune Amplifier suspends data collection when the specified limit is reached.

Note

The size of data stored in the result directory may not exactly match the specified limit due to the following reasons:

  • The collected data may slightly exceed the limit since the VTune Amplifier only checks the data size periodically.

  • During finalization, the VTune Amplifier loads the raw data into a database with additional information about source and binary files.

Slow frames threshold, frames/s

Specify a threshold to separate Slow and Good frames. Frame rates lower than this threshold are marked as Slow. This threshold needs to be smaller than the Fast frames threshold.

Fast frames threshold, frames/s

Specify a threshold to separate Good and Fast frames. Frame rates higher than this threshold are marked as Fast. This threshold needs to be larger than the Slow frames threshold.

CPU mask

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.

Result location options

Select where you want to store your result file. By default, the result is stored in the project directory.

Custom collector

Provide a command line for launching an external collection tool, if any. You can later import the custom collection data (time intervals and counters) in a CSV format to a VTune Amplifier result. Click the Modify button to add a path to your external collector.

VTune Amplifier installation directory on the remote system

Specify a path to the VTune Amplifier on the remote system. If the default location is used, this path is automatically supplied.

Note

This option is available for the remote (Linux or Android) target types.

Temporary directory on the remote system

Specify a path to the /tmp directory on the remote system where performance results are temporarily stored.

Note

This option is available for the remote (Linux or Android) target types.

For more complete information about compiler optimizations, see our Optimization Notice.