A newer version of this document is available. Customers should click here to go to the newest version.
Visible to Intel only — GUID: GUID-38840B3C-04FE-445B-8F4E-B74263009792
Visible to Intel only — GUID: GUID-38840B3C-04FE-445B-8F4E-B74263009792
Containerization Support
Use containers to set up environments for profiling:
You can prepare a container with an environment pre-configured with all the tools you need, then develop within that environment.
You can move that environment to another machine without additional setup.
You can extend containers with different sets of compilers, profilers, libraries, or other components, as needed.
Depending on the setup, Intel® VTune™ Profiler supports the following target types and analyses:
Setup |
Target Type |
Analysis Type |
|---|---|---|
VTune Profiler and app running in the same container |
|
|
VTune Profiler in the container and an app outside the container |
|
|
VTune Profiler outside the container and an app in the container (supported containers: LXC*, Docker, Mesos*, Singularity*) |
|
The Hotspots (hardware event-based sampling mode) and Microarchitecture Exploration analyses are configured to use driver-less data collection based on the Linux Perf* tool.
In the Profile System mode, VTune Profiler profiles all applications running in the same container or in different containers simultaneously. So, the standard limitation for the system-wide profiling of the managed code is not applicable to Java applications running in the containers.
The Attach to Process target type for Java apps is supported only with the Java Development Kit (JDK).
When VTune Profiler and an application are NOT running in the same container, both local and remote target system configurations are available.