Intel® VTune™ Amplifier

Event-based Stack Sampling Analysis Workflow

The following figure shows steps required for extending regular hardware event-based sampling analysis to collect call stacks, threading and power efficiency data. To display more information about a workflow step:

Note

If clicking the workflow step does not display the associated topic, use the text links below the figure.

Prerequisites: Make sure your kernel is configured to enable the event-based stack sampling collection.

Choose an analysis target. Click to learn more.Before running a VTune Amplifier analysis, you have to specify what you want to profile - your analysis target, which could be an executable file, a process, or a whole system. Choose a hardware event-based analysis type. Click to learn more. Enable the Collect stacks option in the analysis configuration. Click to learn more.Enable call stack data collection for hardware event-based sampling analysis types. Run selected analysis type. Click to learn more. Interpret performance, parallelism and power efficiency metrics with regard to execution paths. Click to learn more.

1.

Choose analysis target

Create a project and choose an analysis target using the Configure Project toolbar button. Event-based stack sampling data collection cannot be configured for the entire system. You have to specify an application to launch or attach to.

2.

Choose analysis type

In the Analysis Type window, choose an event-based sampling analysis type with hardware events that fit your task and intention best.

3.

Enable stack analysis in the selected configuration

In the configuration pane for the selected analysis, enable the Collect stacks option. If this option is enabled, you may also select the Estimate call counts checkbox to statistically approximate the number of calls to sampled functions.

4.

Run the selected analysis

Click Start to launch the selected event-based sampling analysis type.

5.

Interpret collected data

Explore the collected data and analyze performance, parallelism and power efficiency metrics with regard to execution paths.

See Also