About Sampling Views (vtl)

This information applies to the command-line interface (vtl) only.

Data gathered with the sampling collector can be displayed in the following views: process view, module view, thread view, and hotspot view. From the data displayed in the sampling views, you can identify hotspots or performance bottlenecks in the operating system modules, your application, and other software modules executing on your system. A high number of samples collected at a specific process, thread, or module can imply high CPU utilization or potential performance bottlenecks.

After collecting sampling data with the VTune(TM) Performance Analyzer, use the view command to view the collected data:

vtl view <ActivityName::ActivityResultName> <options>

where:

• <ActivityName::ActivityResultName> is the name of the Activity and Activity result, for example: a2::r1. If no arguments are specified, the VTune analyzer displays data of the most recent Activity result.

• <options> are any of the sampling view options used to filter the collected data. There are primary, and secondary view options. Secondary options can be used only when preceded with the corresponding primary option.

Primary Options

• [-processes]

• [-modules]

• [-ha | -hotspot-address <-mn <m1>[,m2,...]>]

• [-hf | -hotspot-function <-mn <m1>[,m2,...]>]

• [-threads]

Secondary Options

Filtering Options:

• [-cpu [0,1,..63]]

• [-pid <pid1>[,pid2,...]]

• [-mn | -module-name <m1>[,mn,...]]

• [-pn | -process-name <P1>[,P2,...PN]]

• [-en | -event-name <name>]

The following options are supported for the thread view:

• [-tid]                      

• [-sea | -show-events-as <value>]

• [-sum | -summary]

• [-as | -activity-summary]                             

• [-es | -env-summary]

Formatting Options:

• [-cd | -column-delimiter CHAR]

• [-sort | -sort-by <column_name> <event_name>]

note

Process and module views can be dumped in the same command line.

Command-line example:

>vtl view -modules -processes