Configure Python data collection
Identify hotspots
Understand limitations

Configure Python Data Collection

Click the
Configure Analysis
button on the toolbar.
The Configure Analysis window opens.
Choose a target system and target type. For example:
Local Host
and
Launch Application
.
Only Windows* and Linux* target systems are supported.
In the
Launch Application
configuration pane, specify a path to the installed Python interpreter in the
Application
field and a path to your Python script in the
Application parameters
field.
If you specify a relative path to your Python script in the
Application parameters
field, the
VTune
Profiler
properly resolves full function or method names only for the imported modules, and does not resolve the names inside the main script. Consider specifying the absolute path to the script.
In addition, you may select the
Auto
managed code profiling mode, and the
VTune
Profiler
automatically detects the type of target executable, managed or native, and switches to the corresponding mode. Optionally, you may select
Analyze child processes
option to collect data on processes launched by the target process. For example, on Linux your configuration may look like this:

In case your Python application needs to run before the profiling starts or cannot be launched at the start of this analysis, you may attach the
VTune
Profiler
to the Python process. To do this, select the
Attach to Process
target type and specify the Python process name or PID as follows:

When you attach the
VTune
Profiler
to the Python process, make sure you initialize the Global Interpreter Lock (GIL) inside your script before you start the analysis. If GIL is not initialized, the
VTune
Profiler
collector initializes it only when a new Python function is called.
From the
HOW
configuration pane on the right, select the
Hotspots
,
Threading
, or
Memory Consumption
analysis type.
Configure the following options, if required, or use the defaults:
User-Mode Sampling mode	Select to enable the user-mode sampling and tracing collection for hotspots and call stack analysis (formerly known as Basic Hotspots). This collection mode uses a fixed sampling interval of 10ms. If you need to change the interval, click the Copy button and create a custom analysis configuration.
Hardware Event-Based Sampling mode	Select to enable hardware event-based sampling collection for hotspots analysis (formerly known as Advanced Hotspots). You can configure the following options for this collection mode: CPU sampling interval, ms to specify an interval (in milliseconds) between CPU samples. Possible values for the hardware event-based sampling mode are 0.01-1000 . 1 ms is used by default. Collect stacks to enable advanced collection of call stacks and thread context switches. When changing collection options, pay attention to the Overhead diagram on the right. It dynamically changes to reflect the collection overhead incurred by the selected options.
Show additional performance insights check box	Get additional performance insights, such as vectorization, and learn next steps. This option collects additional CPU events, which may enable the multiplexing mode. The option is enabled by default.
Details button	Expand/collapse a section listing the default non-editable settings used for this analysis type. If you want to modify or enable additional settings for the analysis, you need to create a custom configuration by copying an existing predefined configuration. VTune Profiler creates an editable copy of this analysis type configuration.
Click the
Start
button to run the analysis.

Identifying Hotspots

Limitations