Intel® VTune™ Profiler Performance Analysis Cookbook

Download PDF
ID 766316
Date 9/05/2023
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
Intel® VTune™ Profiler Performance Analysis Cookbook
Intel® VTune™ Profiler Performance Analysis Cookbook x
Methodologies Configuration Recipes Tuning Recipes Notices and Disclaimers
Methodologies x
Top-down Microarchitecture Analysis Method OpenMP* Code Analysis Method Custom Data Collection for Performance Analysis (NEW) Software Optimization for Intel® GPUs (NEW) Core Utilization in DPDK Apps PCIe Traffic in DPDK Apps DPDK Event Device Profiling Effective Utilization of Intel® Data Direct I/O Technology Compile a Portable Optimized Binary with the Latest Instruction Set
Configuration Recipes x
Profiling High Bandwidth Memory Performance on Intel® Xeon® CPU Max Series Profiling Windows* Applications for Hybrid CPU Platforms (NEW) Profiling Machine Learning Applications (NEW) Profiling Single-Node Kubernetes* Applications (NEW) Analyzing Hot Code Paths Using Flame Graphs (NEW) Improving Hotspot Observability in a C++ Application Using Flame Graphs Measuring Performance Impact of NUMA in Multi-Processor Systems Profiling Games built with Unity* (NEW) Profiling Games built with Unreal Engine* (NEW) Profiling Java Applications as a Remote User (NEW) Profiling JavaScript* Code in Node.js* Analyzing CPU and FPGA (Intel® Arria® 10 GX) Interaction Profiling a .NET* Core Application Profiling Applications in Amazon Web Services* (AWS) EC2 Instances Ingredients Before You Begin Create and Configure a Virtual Machine Instance Configure the Instance for Profiling Run Hotspots Analysis See Also Enabling Performance Profiling in GitLab* CI Configuring a Hyper-V* Virtual Machine for Hardware-Based Hotspots Analysis Profiling an Application for Performance Anomalies (NEW) Profiling an OpenMP* Offload Application running on a GPU (NEW) Profiling a SYCL* Application running on a GPU Profiling an FPGA-driven SYCL* Application Profiling Hardware Without Intel Sampling Drivers Profiling MPI Applications Profiling Docker* Containers Profiling a Remote Target Through a Proxy Server (NEW) Profiling in a Singularity* Container Profiling Linux*, Android*, and QNX* System Boot Time Using Intel® VTune™ Profiler Server with Visual Studio Code and Intel® DevCloud for oneAPI (NEW) Using Intel® VTune™ Profiler Server in HPC Clusters Using the Command-Line Interface to Analyze the Performance of a SYCL* Application running on a GPU (NEW)
Tuning Recipes x
Cache-Related Latency Issues in Segmented Cache Environment False Sharing Frequent DRAM Accesses Poor Port Utilization Page Faults Instruction Cache Misses Inefficient Synchronization Inefficient TCP/IP Synchronization OS Thread Migration OpenMP* Imbalance and Scheduling Overhead Processor Cores Underutilization: OpenMP* Serial Time Scheduling Overhead in Intel® Threading Building Blocks (Intel® TBB) Apps PMDK Application Overhead
Intel® VTune™ Profiler Performance Analysis Cookbook

Profiling Applications in Amazon Web Services* (AWS) EC2 Instances

This recipe helps you set up a virtual machine (VM) instance in AWS to profile application performance with Intel® VTune™ Profiler.

Ingredients

This section lists the hardware and software tools used for the performance analysis scenario.

  • Application: Use any application of your choice.

  • Tools: Intel® VTune™ Profiler version 2023 - Hotspots analysis

    NOTE:

    • Starting with the 2020 release, Intel® VTune™ Amplifier has been renamed to Intel® VTune™ Profiler.

    • Most recipes in the Intel® VTune™ Profiler Performance Analysis Cookbook are flexible. You can apply them to different versions of Intel® VTune™ Profiler. In some cases, minor adjustments may be required.

    • Get the latest version of Intel® VTune™ Profiler:

Before You Begin

  • Understand the system requirements to install VTune Profiler on your machine. Your system must have at least 4 GB of RAM and 10 GB of free disk space.

  • Review the functionality of VTune Profiler available for different types of AWS instances.

  • Ensure that the AWS instance can support a connection over SSH (port 22).

  • The storage size for the root volume should be at least 10 GB for data collection and results.

Create and Configure a Virtual Machine Instance

Set up a virtual machine by following instructions on the AWS site.

Configure the Instance for Profiling

Prepare the target instance for profiling. by setting /proc/sys/kernel/yama/ptrace_scope to 0:

  • For User-Mode sampling collections, set /proc/sys/kernel/yama/ptrace_scope to 0: 

    echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope

  • For Hardware Event-Based sampling collections, set /proc/sys/kernel/perf_event_paranoid to 0: 

    echo 0 | sudo tee /proc/sys/kernel/perf_event_paranoid

For more information on driverless profiling, see Profiling Hardware without Intel Sampling Drivers.

Run Hotspots Analysis

Run a Hotspots analysis using one of these methods:

  • Use SSH to run a remote collection from VTune Profiler installed locally

  • Run VTune Profiler directly from the AWS instance

  • Run VTune Profiler as a web service on the AWS instance

Use SSH to run a remote collection from VTune Profiler installed locally:

  1. (Optional) If you have a .pem key for your AWS instance, complete these steps:

    1. In your user home directory, create or open the config file: 

      <user home>\.ssh\config

    2. Add these lines to the config file: 

      Host *.compute.amazonaws.com
User <instance user>
IdentityFile <path-to>\key.pem

    3. If you are using a VPN where a proxy is required, include these lines: 

      LocalForward 4022 c009:22
ProxyCommand "<net connect utility>" -x proxy-server.com:1080 %h %p

  2. Create a project in Intel® VTune™ Profiler.

  3. In the WHERE pane of the Configure Analysis window, select Remote Linux(SSH).

  4. Locate the public IPv4 DNS address for your instance:

  5. In the SSH destination field, enter <instance user>@<public IPv4 DNS for instance>.

    Intel® VTune™ Profiler attempts to connect to the remote system to determine if the binaries necessary for data collection have been installed.

    If you updated the config file in step 1, Intel® VTune™ Profiler uses that configuration and key to connect.

    Otherwise, you should be prompted to enter a password. Intel® VTune™ Profiler then creates its own SSH key and stores it in <user home>/.ssh. The SSH key is then copied to the authorized_keys file of the instance.

  6. If you see a message that the product cannot be found on the target system, click Deploy to install.

  7. In the WHAT pane, specify the location of your application and its working directory.

  8. In the HOW pane, select Hotspots analysis with User-Mode Sampling collection.

  9. Click to start the collection.

Once the analysis completes, Intel® VTune™ Profiler copies the results to your local system for analysis.

Run VTune Profiler directly from the AWS instance:

  1. Install VTune Profiler by following instructions in the Installation Guide.

  2. Run VTune Profiler. For example: 

    sudo <vtune_install_dir>/vtune_profiler/bin64/vtune-gui

  3. Create a project.

  4. In the Configure Analysis window,

    • In the WHERE pane, select Local Host.

    • In the WHAT pane, specify the location of your application and its working directory.

    • In the HOW pane, select a preferred collection mode for the Hotspots analysis. For example, select Hardware Event-Based Sampling.

  5. Click to start the collection.

The analysis result opens in the Hotspots by CPU Utilization viewpoint.

Run VTune Profiler as a Web Service on the AWS Instance:

  1. Install VTune Profiler by following instructions in the Installation Guide.

  2. Run the VTune Profiler Web Service: 

    <vtune_install_dir>/latest/bin64/vtune-backend –-allow-remote-access –-enable-server-profiling –-web-port=8080

    The vtune-backend command returns a URL with the private IP for the instance as well as a one-time token.

  3. Replace the private IP with the public IP or DNS for the instance. For example, https://172.29.129.54:8080/?one-time-token=b8cafc89721e781161aba4ddcef5a718 becomes https://18.236.194.236:8080/?one-time-token=b8cafc89721e781161aba4ddcef5a718.

  4. Copy the URL into your browser.

    NOTE:
    The browser may display a warning indicating that the URL might be unsafe. This is because the web service is using a self-signed certificate instead of an officially signed certificate.

  5. Create a passphrase at the prompt and proceed to the VTune GUI.

  6. Select Add new remote target.

  7. In the Configure Analysis window,

    • In the WHERE pane, select Local Host.

    • In the WHAT pane, specify the location of your application and its working directory.

    • In the HOW pane, select a preferred collection mode for the Hotspots analysis. For example, select Hardware Event-Based Sampling.

  8. Click to start the collection.

The analysis result opens in the Hotspots by CPU Utilization viewpoint.

Parent topic: Configuration Recipes
Level Two Title