Module View (vtl) Module View (vtl) This information applies to the command-line interface (vtl) only.
Modules are executable binary image files. The module view displays all the modules specified by ID or name of the processes that were running during the period of sampling. This is the default view.
To view module data from the command line, use the -modules option.
Command-line example:
>vtl view a2::r1 -modules
where a2 - Activity name, r1 - Activity result name.
Use the information from the module view for the hotspot analysis. Modules that have been called frequently during sampling data collection are displayed as ones with the highest number of events or the most CPU time.
For event-based sampling, the module view displays the event totals (for each event) for every module that executed. Collected data are displayed in the table format:
Column Heading |
Description |
|---|---|
|
Modules |
Modules for which data was collected. |
|
Process |
Names of the processes that called each module. |
|
Event |
Event name. |
|
CPU |
Logical CPU where the samples were collected. |
|
Events |
Total event count for each module. The event count is based on the number of samples collected for the module x Sample After value. |
|
%Events |
Per cent of all events counted in this CPU-process-module combination during the data collection. For example, if 1000 Clockticks events were counted during the data collection and 100 of the Clockticks events were counted in the vtl module (cpu 0, vtl process), 10% of the Clockticks events will be attributed to the cpu0-vtl module-vtl process module. |
|
<Event name> CPU<n> events |
Number of events that occurred on each processor for every module. |
|
<Event ratio name> |
The dynamically calculated sample count for the event ratios. These values depend on the event counts for the selected events. |
|
Samples |
Samples collected in the CPU-process-module combination due to a specific event. |
|
Process Path |
Paths of the processes that called each module, during profiling. |
|
Process ID |
The system provides each process with an ID to distinguish it from the other. |
|
Module Path |
Paths of the modules during profiling. |
Modules that took the most CPU time (compare the Timer or the Clockticks event columns).
Modules that generated the highest event totals to determine potential microarchitecture level performance problems.
Performance of your module in relation to others.
noteProcess and module views can be dumped in the same command line.
Command-line example:
>vtl view -modules -processes