Intel® VTune™ Profiler

User Guide

Download PDF
ID 766319
Date 6/24/2024
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents
Document Table of Contents x
User Guide
User Guide x
Introduction Install Intel® VTune™ Profiler Open Intel® VTune™ Profiler Set Up Project Set Up Analysis Target Analyze Performance Intel® VTune™ Profiler Command Line Interface API Support Troubleshooting Reference Notices and Disclaimers
Introduction x
Tuning Methodology Tutorials and Samples Notational Conventions Get Help Product Website and Support Related Information
Install Intel® VTune™ Profiler x
Sampling Drivers Set Up System for GPU Analysis Verify Intel® VTune™ Profiler Installation Install VTune Profiler Server Security Best Practices
Set Up System for GPU Analysis x
Rebuild and Install the Kernel for GPU Analysis Rebuild and Install Module i915 for GPU Analysis on CentOS* Rebuild and Install Module i915 for GPU Analysis on Ubuntu*
Install VTune Profiler Server x
Set Up Transport Security Configure User Authentication/Authorization
Open Intel® VTune™ Profiler x
Get Started with Intel® VTune™ Profiler Intel® VTune™ Profiler Graphical User Interface Web Server Interface Run VTune Profiler Server Deploy the VTune Profiler Agent Shared Agents Select a Client System Select a Remote System Run the Analysis Analyze Process Running Under Arbitrary Account (Linux* OS) Control VTune Profiler Agents See Also Microsoft Visual Studio* Integration Eclipse* and Intel System Studio IDE Integration Containerization Support
Containerization Support x
Run VTune Profiler in a Container Profile Container Targets from the Host
Set Up Project x
WHERE: Analysis System WHAT: Analysis Target HOW: Analysis Types Search Directories
WHERE: Analysis System x
Analysis System Options
WHAT: Analysis Target x
Analysis Target Options
Search Directories x
Search Order
Set Up Analysis Target x
Prepare Application for Analysis Windows* Targets Linux* Targets Embedded Linux* Targets FreeBSD* Targets QNX* Targets Managed Code Targets Android* Targets Intel® Xeon Phi™ Processor Targets Targets in Virtualized Environments Targets in a Cloud Environment Arbitrary Targets Embedded System Targets
Windows* Targets x
Install the Sampling Drivers for Windows* Targets Debug Information for Windows* Application Binaries Compiler Switches for Performance Analysis on Windows* Targets Debug Information for Windows* System Libraries Add Administrative Privileges
Linux* Targets x
Build and Install the Sampling Drivers for Linux* Targets Debug Information for Linux* Application Binaries Compiler Switches for Performance Analysis on Linux* Targets Enable Linux* Kernel Analysis Resolution of Symbol Names for Linux-Loadable Kernel Modules Analyze Statically Linked Binaries on Linux* Targets Set Up Remote Linux* Target
Set Up Remote Linux* Target x
Set Up Linux* System for Remote Analysis Configure SSH Access for Remote Collection Search Directories for Remote Linux* Targets Temporary Directory for Performance Results on Linux* Targets
Embedded Linux* Targets x
Configure Yocto Project* and VTune Profiler with the Integration Layer Configure Yocto Project*/Wind River* Linux* and Intel® VTune™ Profiler with the Intel System Studio Integration Layer Configure Yocto Project* and Intel® VTune™ Profiler with the Linux* Target Package
FreeBSD* Targets x
Set Up FreeBSD* System
Managed Code Targets x
.NET* Targets Windows Store Application Targets Go* Application Targets
Android* Targets x
Build and Install Sampling Drivers for Android* Targets Set Up Android* System Enable Java* Analysis on Android* System Prepare an Android* Application for Analysis Analyze Unplugged Devices Search Directories for Android* Targets
Targets in Virtualized Environments x
Profile Targets on a VMware* Guest System Profile Targets on a Parallels* Guest System Profile Targets on a KVM* Guest System Profile Targets on a Xen* Virtualization Platform Profile Targets in the Hyper-V* Environment
Profile Targets on a KVM* Guest System x
Profile KVM Kernel Modules from the Host Profile KVM Kernel and User Space on the KVM System Profile KVM Kernel and User Space from the Host
Analyze Performance x
User-Mode Sampling and Tracing Collection Hardware Event-based Sampling Collection Performance Snapshot Algorithm Group Microarchitecture Analysis Group Parallelism Analysis Group Input and Output Analysis Accelerators Analysis Group Platform Analysis Group Platform Analysis Hybrid CPU Analysis Source Code Analysis Custom Analysis Energy Analysis Code Profiling Scenarios Control Data Collection Manage Data Views Manage Result Files
Hardware Event-based Sampling Collection x
Allow Multiple Runs or Multiplex Events Hardware Event-based Sampling Collection with Stacks
Algorithm Group x
Hotspots Analysis for CPU Usage Issues Anomaly Detection Analysis (preview) Memory Consumption Analysis
Hotspots Analysis for CPU Usage Issues x
Hotspots View
Anomaly Detection Analysis (preview) x
Anomaly Detection View
Memory Consumption Analysis x
Memory Consumption and Allocations View
Microarchitecture Analysis Group x
Microarchitecture Exploration Analysis for Hardware Issues Memory Access Analysis for Cache Misses and High Bandwidth Issues
Microarchitecture Exploration Analysis for Hardware Issues x
Microarchitecture Exploration View Microarchitecture Pipe
Memory Access Analysis for Cache Misses and High Bandwidth Issues x
Memory Usage View
Parallelism Analysis Group x
Threading Analysis HPC Performance Characterization Analysis
Threading Analysis x
Threading Efficiency View
HPC Performance Characterization Analysis x
HPC Performance Characterization View
Input and Output Analysis x
Analyze Platform Performance Analyze DPDK Applications Analyze SPDK Applications Analyze Linux Kernel I/O
Accelerators Analysis Group x
GPU Offload Analysis GPU Compute/Media Hotspots Analysis (Preview) CPU/FPGA Interaction Analysis NPU Exploration Analysis
GPU Compute/Media Hotspots Analysis (Preview) x
GPU Compute/Media Hotspots View
CPU/FPGA Interaction Analysis x
CPU/FPGA Interaction View
NPU Exploration Analysis x
NPU Exploration View
Platform Analysis Group x
System Overview Analysis
System Overview Analysis x
Analyze Interrupts Analyze Latency Issues
Custom Analysis x
Custom Analysis Options
Custom Analysis Options x
Highly Accurate CPU Time Data Collection Hardware Event List Linux* and Android* Kernel Analysis Sampling Interval Sample After Value
Hardware Event List x
Hardware Event Skid Instructions Retired Event Precise Events
Energy Analysis x
Run Energy Analysis View Energy Analysis Data with Intel® VTune™ Profiler Interpret Energy Analysis Data with Intel® VTune™ Profiler
Code Profiling Scenarios x
Java* Code Analysis Python* Code Analysis Intel® Threading Building Blocks Code Analysis MPI Code Analysis OpenSHMEM* Code Analysis with Fabric Profiler GPU Application Analysis on Intel® HD Graphics and Intel® Iris® Graphics Frame Data Analysis Task Analysis
GPU Application Analysis on Intel® HD Graphics and Intel® Iris® Graphics x
GPU OpenCL™ Application Analysis Intel® Media SDK Program Analysis
Control Data Collection x
Finalization Pause Data Collection Limit Data Collection Generate Command Line Configuration from GUI Minimize Collection Overhead Import External Data
Import External Data x
Use a Custom Collector Create a CSV File with External Data Import Linux Perf* Trace with VTune Profiler Metrics Examples of CSV Format and Imported Data
Manage Data Views x
Switch Viewpoints Control Window Synchronization View Stacks Manage Grid Views Manage Timeline View Change Threshold Values Choose Data Format Group and Filter Data View Data on Inline Functions Analyze Loops Stitch Stacks for Intel® oneAPI Threading Building Blocks or OpenMP* Analysis Search for Data
View Stacks x
Call Stack Mode Metrics Distribution Over Call Stacks
Manage Result Files x
VTune Profiler Filenames and Locations Import Results and Traces into VTune Profiler GUI Compare Results
Compare Results x
Compare Source Code View Comparison Data
View Comparison Data x
Comparison Summary Bottom-up Comparison Top-down Tree Comparison
Intel® VTune™ Profiler Command Line Interface x
vtune Command Syntax vtune Actions Run Command Line Analysis Work with Results from Command Line Generate Command Line Reports Command Line Usage Scenarios Command Line Interface Reference Report Problems from Command Line
Run Command Line Analysis x
performance-snapshot Command Line Analysis hotspots Command Line Analysis anomaly-detection Command Line Analysis threading Command Line Analysis memory-consumption Command Line Analysis hpc-performance Command Line Analysis uarch-exploration Command Line Analysis memory-access Command Line Analysis tsx-exploration Command Line Analysis tsx-hotspots Command Line Analysis sgx-hotspots Command Line Analysis gpu-hotspots Command Line Analysis gpu-offload Command Line Analysis npu graphics-rendering Command Line Analysis fpga-interaction Command Line Analysis io Command Line Analysis system-overview Command Line Analysis runsa/runss Custom Command Line Analysis Configure Analysis Options from Command Line
Configure Analysis Options from Command Line x
Collect System-Wide Data from Command Line Collect Data on Remote Linux* Systems from Command Line Configure GPU Analysis from Command Line Specify Search Directories from Command Line Specify Result Directory from Command Line Pause Collection from Command Line Manage Analysis Duration from Command Line Limit Data Collection from Command Line
Work with Results from Command Line x
View Command Line Results in the GUI Import Results from Command Line Re-finalize Results from Command Line
Generate Command Line Reports x
Summary Report Hotspots Report Hardware Events Report Callstacks Report Timeline Report Top-down Report GPU Compute/Media Hotspots Report gprof-cc Report Difference Report View Source Objects from Command Line Save and Format Command Line Reports Filter and Group Command Line Reports
Command Line Usage Scenarios x
Use VTune Profiler Server in Containers Android* Target Analysis from the Command Line OpenMP* Analysis from the Command Line Java* Code Analysis from the Command Line
Command Line Interface Reference x
Option Descriptions and General Rules allow-multiple-runs analyze-kvm-guest analyze-system app-working-dir archive call-stack-mode collect collect-with column command cpu-mask csv-delimiter cumulative-threshold-percent custom-collector data-limit discard-raw-data duration filter finalization-mode finalize format group-by help import inline-mode knob kvm-guest-kallsyms kvm-guest-modules limit loop-mode mrte-mode no-follow-child no-summary no-unplugged-mode quiet report report-knob report-output report-width result-dir resume-after return-app-exitcode ring-buffer search-dir show-as sort-asc sort-desc source-object source-search-dir stack-size start-paused strategy target-install-dir target-system target-tmp-dir target-duration-type target-pid target-process time-filter trace-mpi user-data-dir verbose version
API Support x
Support for Instrumentation and Tracing Technology API (ITT API) JIT Profiling API System APIs Supported by Intel® VTune™ Profiler
Support for Instrumentation and Tracing Technology API (ITT API) x
Basic Usage and Configuration Instrumentation and Tracing Technology API Reference
Basic Usage and Configuration x
Configure Your Build System Attach ITT APIs to a Launched Application Instrument Your Application Minimize ITT API Overhead View Instrumentation and Tracing Technology (ITT) API Task Data in Intel® VTune™ Profiler
Instrumentation and Tracing Technology API Reference x
Domain API String Handle API Collection Control API Thread Naming API Task API Frame API Histogram API User-Defined Synchronization API Event API Counter API Context Metadata API Load Module API Memory Allocation APIs
JIT Profiling API x
Using JIT Profiling API JIT Profiling API Reference
JIT Profiling API Reference x
iJIT_NotifyEvent iJIT_IsProfilingActive iJIT_ GetNewMethodID
Troubleshooting x
Best Practices: Resolve Intel® VTune™ Profiler BSODs, Crashes, and Hangs in Windows* OS Error Message: Application Sets Its Own Handler for Signal Error Message: Cannot Enable Event-Based Sampling Collection Error Message: Cannot Collect GPU Hardware Metrics Error Message: Cannot Load Data File Error Message: Cannot Locate Debugging Information Error Message: Cannot Open Data Error Message: Client Is Not Authorized to Connect to Server Error Message: Root Privileges Required for Processor Graphics Events Error Message: No Pre-built Driver Exists for This System Error Message: Not All OpenCL™ API Profiling Callbacks Are Received Error Message: Problem Accessing the Sampling Driver Error Message: Required Key Not Available Error Message: Scope of ptrace System Call Is Limited Error Message: Stack Size Is Too Small Error Message: Symbol File Is Not Found Problem: Analysis of the .NET* Application Fails Problem: Cannot Access VTune Profiler Documentation Problem: CPU time for Hotspots or Threading Analysis is Too Low Problem: 'Events= Sample After Value (SAV) * Samples' Is Not True If Multiple Runs Are Disabled Problem: Guessed Stack Frames Problem: GUI Hangs or Crashes Problem: Inaccurate Sum in the Grid Problem: Information Collected via ITT API Is Not Available When Attaching to a Process Problem: No GPU Utilization Data Is Collected Problem: Same Functions Are Compared As Different Instances Problem: Skipped Stack Frames Problem: Stack in the Top-Down Tree Window Is Incorrect Problem: Stacks in Call Stack and Bottom-Up Panes Are Different Problem: System Functions Appear in the User Functions Only Mode Problem: Intel® VTune™ Profiler is Slow to Respond When Collecting or Displaying Data Problem: Intel® VTune™ Profiler is Slow on X-Servers with SSH Connection Problem: Unexpected Paused Time Problem: {Unknown Timer} in the Platform Power Analysis Viewpoint Problem: Unknown Critical Error Due to Disabled Loopback Interface Problem: Unknown Frames Problem: Unsupported Microsoft* Windows* OS Warnings about Accurate CPU Time Collection
Reference x
User Interface Reference CPU Metrics Reference GPU Metrics Reference OpenCL™ Kernel Analysis Metrics Reference Energy Analysis Metrics Reference Intel Processor Events Reference
User Interface Reference x
Context Menu: Grid Context Menus: Call Stack Pane Context Menus: Project Navigator Context Menus: Source/Assembly Window Dialog Box: Binary/Symbol Search Dialog Box: Source Search Hot Keys Menu: Customize Grouping Menu: Intel VTune Profiler Pane: Call Stack Pane: Options - General Pane: Options - Result Location Pane: Options - Source/Assembly Project Navigator Pane: Timeline Toolbar: Configure Analysis Toolbar: Filter Toolbar: Source/Assembly Toolbar: Intel VTune Profiler Window: Bandwidth - Platform Power Analysis Window: Bottom-up Window: Caller/Callee Window: Cannot Find <file type> File Window: Collection Log Window: Compare Results Window: Configure Analysis Window: Core Wake-ups - Platform Power Analysis Window: Correlate Metrics - Platform Power Analysis Window: CPU C/P States - Platform Power Analysis Window: Debug Window: Event Count - Hardware Events Window: Flame Graph Window: Graphics - GPU Compute/Media Hotspots Window: Graphics C/P States - Platform Power Analysis Window: NC Device States - Platform Power Analysis Window: Platform Window: Platform Power Analysis Window: Sample Count - Hardware Events Window: SC Device States - Platform Power Analysis Window: Summary Window: System Sleep States - Platform Power Analysis Window: Temperature/Thermal Sample - Platform Power Analysis Window: Timer Resolution - Platform Power Analysis Window: Top-down Tree Window: Uncore Event Count - Hardware Events Window: Wakelocks - Platform Power Analysis
Window: Summary x
Window: Summary - Input and Output Summary Window: Summary - Microarchitecture Exploration Window: Summary - GPU Analysis Window: Summary - Hardware Events Window: Summary - Hotspots by CPU Utilization Window: Summary - HPC Performance Characterization Window: Summary - Memory Consumption Window: Summary - Memory Usage Window: Summary - Platform Power Analysis
GPU Metrics Reference x
ALU0 Active ALU0 Instructions ALU1 Active ALU1 Instructions ALU2 Active ALU2 Instructions ALU0 and ALU1 Active ALU0 and ALU2 Active Average Time Computing Threads Started Computing Threads Started, Threads/sec CPU Time EU 2 FPU Pipelines Active EU Array Active EU Array Idle EU Array Stalled/Idle EU Array Stalled EU IPC Rate EU Send pipeline active EU Threads Occupancy Host to GPU Memory Read Bandwidth Host-to-GPU Memory Write Bandwidth Global GPU EU Array Usage GPU L3 Bound GPU L3 Miss Ratio GPU L3 Misses GPU L3 Misses, Misses/sec GPU Memory Read Bandwidth, GB/sec GPU Memory Texture Read Bandwidth, GB/sec GPU Memory Write Bandwidth, GB/sec GPU Texel Quads Count, Count/sec GPU Utilization Instance Count L3 Read Bandwidth L3 Write Bandwidth L3 Sampler Bandwidth, GB/sec L3 Shader Bandwidth, GB/sec LLC Miss Rate due GPU Lookups LLC Miss Ratio due GPU Lookups Local Maximum GPU Utilization Occupancy PS EU Active % PS EU Stall % Ratio to Max Bandwidth, % Ratio to Max Bandwidth, % Ratio to Max Bandwidth, % Render/GPGPU Command Streamer Loaded Samples Blended Samples Killed in PS, pixels Samples Written Sampler Busy Sampler Is Bottleneck Shared Local Memory Read Bandwidth, GB/sec Shared Local Memory Write Bandwidth, GB/sec SIMD Width Stack-to-stack Incoming Bandwidth Stack-to-stack Outgoing Bandwidth System Memory Read Bandwidth System Memory Write Bandwidth Size Total, GB/sec Total Time Typed Memory Read Bandwidth, GB/sec Typed Memory Write Bandwidth, GB/sec Typed Reads Coalescence Typed Writes Coalescence Untyped Memory Read Bandwidth, GB/sec Untyped Memory Write Bandwidth, GB/sec Untyped Reads Coalescence Untyped Writes Coalescence VS EU Active VS EU Stall
OpenCL™ Kernel Analysis Metrics Reference x
Computing Task Total Time Instance Count SIMD Width SIMD Utilization Work Size
Energy Analysis Metrics Reference x
Available Core Time C-State D0ix States DRAM Self Refresh Energy Consumed (mJ) Idle Wake-ups P-State S0ix States Temperature Timer Resolution Total Time in C0 State Total Time in Non-C0 States Total Time in S0 State Total Wake-up Count Wake-ups Wake-ups/sec per Core
User Guide

Web Server Interface

Use Intel® VTune™ Profiler in a web server mode to get an easy on-boarding experience, benefit from a collaborative multi-user environment, and access a common repository of collected performance results.

The web server interface helps you quickly get started with the tool since you do not need to install VTune Profiler as a desktop application on every client system. You can use the VTune Profiler Server to configure and control analysis on arbitrary target systems and view collected results.

To run an analysis via a web interface:

  1. (Personal mode) Run the VTune Profiler Server to get a URL to access the web interface.

    (Reverse proxy/SAML SSO modes) Get the server URL from your admin.

  2. Access the server via the URL.

  3. Deploy the VTune Profiler Agent

  4. Select your target system:

  5. Run the analysis

To control VTune Profiler agents, use the Administrator Dashboard.

Run VTune Profiler Server

Prerequisite: VTune Profiler Server is installed with VTune Profiler GUI.

In the personal/evaluation usage mode, run the VTune Profiler Server as follows:

  1. Start the VTune Profiler Server: 

    <vtune-install-dir>/bin64/vtune-backend

    If you want the VTune Profiler Server to access a specific TCP port, specify it with the --web-port option. For example: 

    vtune-backend --web-port=8080

    VTune Profiler Server outputs a URL to access the GUI. For the first run, the URL includes a one-time token. For example: 

    Serving GUI at https://127.0.0.1:64880?one-time-token=0160852eeff593e0ab0a0f90991b4efa

    Optionally, you can specify a working directory for VTune Profiler Server using the --data-directory option. For example: 

    vtune-backend --web-port=8080 --data-directory="C:\vtune-results"
    NOTE:
    Additional command-line options are available to make the usage of VTune Profiler Server in containers more convenient. See Use VTune Profiler Server in Containers for details.

    VTune Profiler Server allows you to create a directory with a custom hierarchy, organized to best fit your needs. Once you point VTune Profiler Server to this directory using the --data-directory option, users will be able to access all projects and results, regardless of folder names and levels of nesting. This can be especially useful if you're using an HPC scheduler to regularly collect VTune Profiler performance data and put it into a shared folder on the network for later examination. For example, you can organize your results folder by users and their workloads:

    NOTE:
    • By default, access to the VTune Profiler Server is limited to the local host only. To enable access from remote client and target systems, restart the server with the --allow-remote-access option.
    • By default, server host profiling is not enabled. To enable the server host profiling, restart the server with the --enable-server-profiling option.

  2. Open the URL with the provided one-time token.

    NOTE:

    If you start the VTune Profiler Server in the personal/evaluation mode with no signed TLS certificate provided, your web browser warns you that the default self-signed server certificate is not trusted and asks for your confirmation to proceed.

  3. Set a passphrase in the Set Passphrase dialog box.

In the reverse proxy or SAML SSO usage modes, use the URL provided by your admin to access the VTune Profiler Server instance installed in a lab.

Deploy the VTune Profiler Agent

You can choose between automated and manual deployment of the VTune Profiler Agent.

Deploy the Agent automatically

NOTE:

VTune Profiler Server uses SSH for automated agent deployment. Running an SSH server on the target machine is required for automated deployment.

To deploy the Agent automatically:

  1. Enter the target machine username.

  2. Enter the credentials for target machine:

    • For Public key authentication, add your public SSH key to the authorized_keys file on the target system for the user account that you specify in the Username field. Then, select the Private key file on your client machine. If your private key is encrypted, specify the Private key passphrase.

    • Alternatively, switch to Password authentication and provide the username and password.

  3. Optionally, specify the deployment directory.

  4. Click the Deploy Agent button.

Deploy VTune Profiler Agent

Deploy the Agent manually

To deploy the Agent manually:

  1. Click the Download Agent Manually button In the WHERE pane of the Configure Analysis window or access the http://<VTune Profiler Server URL>/api/collection-agent/download URL to download the Agent.

    NOTE:

    You can use tools such as wget to download the Agent directly to the target system.

  2. Extract the Agent archive with your tool of choice and copy its contents to the target system.

  3. Run the vtune-agent executable on the target system and specify the agent owner using the -owner <vtune-user-id> option.

    NOTE:

    You can find your VTune Profiler user ID in the About dialog.

  4. Compare the Agent key fingerprint in the WHERE pane of the Configure Analysis window with the fingerprint printed out by the agent upon startup. If they match, click the Admit Agent button.

Shared Agents

You can run a shared VTune Profiler Agent. In this case, the Agent will be available to all users of an instance of VTune Profiler Server. This means that any user of this VTune Profiler Server instance will be able to run data collection using this agent. It is recommended to only run shared agents using dedicated faceless accounts.

To deploy a shared agent, check the Share the agent with all VTune Profiler users checkbox in the WHERE pane of the Configure Analysis dialog, or use the --shared command line option when deploying an agent manually.

Select a Client System

To profile a client system, which is the same machine that you use to access the VTune Profiler Server via a web browser, do the following:

  1. Click New Project and specify a name for the new project.

    VTune Profiler opens the project configuration with your localhost pre-selected as a target system.

  2. Configure your analysis target and analysis type.

Select a Remote System

To profile a remote target system, do the following:

  1. In the WHERE pane of the Configure Analysis window, click the down arrow to see available target systems.

  2. Select Add new remote target....

    NOTE:

    VTune Profiler maintains a list of used remote systems, if any, and displays it under Remote Targets.

  3. Enter the hostname or IP address.

Run the Analysis

Once the Agent is running, the Configure Analysis pane displays information that VTune Profiler is detecting the device configuration.

The Agent downloads the collectors and the target package, which is approximately 100MB in size. Once the target package is downloaded, the Agent analyzes the target system configuration and displays the applicable analysis types.

To run an analysis:

  1. Install the Intel sampling drivers manually by running these commands:

    On Windows* OS:

    <vtune-agent-dir>\bin64\amplxe-sepreg.exe

    On Linux* OS:

    <vtune-agent-dir>/sepdk/src/build-driver

    <vtune-agent-dir>/sepdk/src/insmod-sep

    The <vtune-agent-dir> is the <vtune_profiler_<version>> installation folder created on the client system by VTune Profiler.

  2. Configure your analysis target and analysis type.
  3. Click the Start button to run the analysis.

Analyze Process Running Under Arbitrary Account (Linux* OS)

VTune Profiler Server provides a way to analyze a process that is running under an arbitrary user account. A common example is analyzing a process in Attach to Process mode that was previously started under an arbitrary user account. The account running the process is not necessarily the same as the account the VTune Profiler Agent was deployed for.

To enable this functionality, provide the following wrapper script in the Advanced Options section of the WHAT pane: 

#!/bin/sh
#Run VTune collector as the target process owner
sudo -C 65000 -A -u <target process owner> "$@"

The sudo command call runs the VTune Profiler collector under the account specified under <target process owner>. Replace this placeholder with the account name under which the target process is running.

If the target workload or the collector request a sudo elevation during the analysis, VTune Profiler Server requests this password interactively in the Web Interface:


NOTE:
  • The interactive sudo elevation requires that the VTune Profiler Agent is deployed under an account that has sudo privileges. To achieve that, ensure that the Username that you provide during deployment belongs to an account with sudo privileges.
  • VTune Profiler provides the password directly to the target system and does not store the password.

Control VTune Profiler Agents

The Administrator Dashboard feature of VTune Profiler Server enables you to monitor and manage one or multiple agents from a single point.

To open the Administrator Dashboard:

  1. Open the VTune Profiler Server interface in your browser.

  2. In the main toolbar, open the drop-down menu and select Administrator Dashboard.

    The dashboard opens in a new tab and shows all agents that are related to this instance of VTune Profiler Server. This includes both connected and disconnected agents.

The dashboard enables you to:

  • View information related to this agent:

    • Target system IP address and hostname

    • The username of the agent's user.

    • Current connection status.

  • Admit or stop one or multiple agents. To admit or stop multiple agents, select the agents by ticking the checkboxes and click Admit selected or Stop selected.

Parent topic: Open Intel® VTune™ Profiler

See Also

Install VTune Profiler Server Set up Intel® VTune™ Profiler as a web server, using a lightweight deployment intended for personal use or a full-scale corporate deployment supporting multi-user environment.
Level Two Title