User Guide

Contents

uarch-exploration
Command Line Analysis

Use the
uarch-exploration
value to launch the Microarchitecture Exploration analysis (formerly known as General Exploration) that is a good starting point to triage hardware issues in your application. Once you have used Hotspots analysis to determine hotspots in your code, you can perform Microarchitecture Exploration analysis to understand how efficiently your code is passing through the core pipeline. During Microarchitecture Exploration analysis,
Intel® VTune™
Profiler
collects a complete list of events for analyzing a typical client application. It calculates a set of predefined ratios used for the metrics and facilitates identifying hardware-level performance problems.

Syntax

vtune
-collect uarch-exploration [-knob [
knobName=knobValue
]] [--] <
target
>
By default, the Microarchitecture Exploration analysis runs in the
detailed
PMU collection mode and collects sub-metrics for all top-level metrics: CPU Bound, Memory Bound, Front-End Bound, Bad Speculation, and Retiring. If required, you may configure the
knob
option to disable collecting sub-metrics for a particular top-level metric.
  • For the most current information on available knobs (configuration options) for the Microarchitecture Exploration analysis, enter:
    vtune
    -help collect uarch-exploration
  • The
    general-exploration
    analysis type value is deprecated. Make sure to use the
    uarch-exploration
    option instead.
Examples
This example runs the Microarchitecture Exploration analysis on a Linux*
matrix
app with enabled memory bandwidth analysis:
vtune -collect uarch-exploration -knob collect-memory-bandwidth=true -- /home/test/matrix
This example runs the Microarchitecture Exploration analysis on a Windows
matrix
app in the low-overhead
summary
profiling mode:
vtune -collect uarch-exploration -knob pmu-collection-mode=summary -- C:\samples\matrix.exe
This example runs the Microarchitecture Exploration analysis on a Linux
matrix
app in the default
detailed
profiling mode but disables the collection of the sub-metrics for the Bad Speculation and Core Bound top-level metrics:
vtune -collect uarch-exploration -knob collect-bad-speculation=false -knob collect-core-bound=false -- /home/test/myApplication

What's Next

When the data collection is complete, do one of the following to view the result:

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.