インテル® VTune™ Amplifier 2018 ヘルプ
Use this configuration to specify an application (a binary or a script) to analyze with the Intel® VTune™ Amplifier on the remote Linux* system via SSH connection.
Prerequisites: Make sure to prepare your target Linux system for analysis:
Set up a password-less SSH access to the target using RSA keys.
Install the VTune Amplifier target package with data collectors on the target Linux system.
If you choose to install the target package to a non-default location, make sure to specify the correct path either with the VTune Amplifier installation directory on the remote system option in the Analysis Target tab (GUI) or with the -target-install-dir option (CLI).
Build the drivers on the host (if required), copy them to the target system and install the drivers.
To build the sampling driver as RPM using build services as Open Build Service (OBS), use the sepdk.spec file located at <install_dir>/sepdk/src the directory.
To access the analysis target configuration:
Open the Analysis Target window and select the remote Linux (SSH) target system from the left pane.
The SSH destination field shows up.
In the SSH destination field, specify the username, hostname, and port (if required) for your remote Linux machine as username@hostname[:port].
Select the Launch Application target type.
Use This |
To Do This |
---|---|
Inherit settings from Visual Studio project check box (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. |
Application field |
Specify a full path to the application to analyze, which can be a binary file or script. |
Application parameters field |
Specify input parameters for your application. |
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. |
Automatically resume collection after (sec) field |
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) field |
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 |
---|---|
VTune Amplifier installation directory on the remote system field |
Specify a path to VTune Amplifier on the remote system. If the default location is used, this path is automatically supplied. |
Temporary directory on the remote system field |
Specify a path to the /tmp directory on the remote system where performance results are temporarily stored. |
Analyze child processes check 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 Configuration where 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. The Default process 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 (self value) and the child processes they spawn (children value). This option is not applicable to hardware event-based analysis types. |
Duration time estimate menu (deprecated) |
NoteThis option is deprecated. Use the CPU sampling interval option on the Analysis Type configuration 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 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. |
Limit collected data by section |
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:
NoteThe size of data stored in the result directory may not exactly match the specified result size due to the following reasons:
|
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. |
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. |
Trace MPI check box (Linux targets only) |
Configure collectors to trace MPI code and determine MPI rank IDs in case of a non-Intel MPI library implementation. |
Result location options |
Select where you want to store your result file. By default, the result is stored in the project directory. |
Click the Choose Analysis button on the right to switch to the Analysis Type tab for selecting, configuring, and launching an analysis. The Analysis Type tab displays analysis types applicable to the specified target type.
You can launch an analysis only for targets accessible from the current host. For an arbitrary target, you can only generate a command line configuration, save it to the buffer and later launch it on the intended host.