For dynamic metrics, those based on measured data, a metric keyword consists of three parts: a metric flavor string, a metric visibility string, and a metric name string. These are joined with no spaces, as follows.
For static metrics, those based on the static properties of the load objects in the experiment (name, address, and size), a metric keyword consists of a metric name, optionally preceded by a metric visibility string, joined with no spaces:
The metric flavor and metric visibility strings are composed of flavor and visibility characters.
The allowed metric flavor characters are listed in Table 5–1. A metric keyword that contains more than one flavor character is expanded into a list of metric keywords. For example, ie.user is expanded into i.user:e.user.
The allowed metric visibility characters are listed in Table 5–2. The order of the visibility characters in the visibility string does not affect the order in which the corresponding metrics are displayed. For example, both i%.user and i.%user are interpreted as i.user:i%user .
Metrics that differ only in the visibility are always displayed together in the standard order. If two metric keywords that differ only in the visibility are separated by some other keywords, the metrics appear in the standard order at the position of the first of the two metrics.
When both flavor and visibility strings have more than one character, the flavor is expanded first. Thus, ie.%user is expanded to i.%user:e.%user, which is then interpreted as i.user:i%user:e.user:e%user .
For static metrics, the visibility characters period (.), plus (+), and percent sign (%), are equivalent for the purposes of defining the sort order. Thus, sort i%user, sort i.user, and sort i+user all mean that Performance Analyzer should sort by inclusive user CPU time if it is visible in any form. sort i!user means Performance Analyzer should sort by inclusive user CPU time, regardless of whether it is visible.
You can use the visibility character exclamation point (!) to override the built-in visibility defaults for each flavor of metric.
If the same metric appears multiple times in the metric list, only the first appearance is processed and subsequent appearances are ignored. If the named metric is not on the list, it is appended to the list.
Table 5–3 lists the available er_print metric name strings for timing metrics, synchronization delay metrics, memory allocation metrics, MPI tracing metrics, and the two common hardware counter metrics. For other hardware counter metrics, the metric name string is the same as the counter name. You can display a list of all the available metric name strings for the loaded experiments with the metric_list command. To list the counter names, issue the collect -h command with no additional arguments. See Hardware Counter Profiling Data for more information on hardware counters.
In addition to the name strings listed in Table 5–3, two name strings can be used only in default metrics lists. These are hwc, which matches any hardware counter name, and any, which matches any metric name string. Also note that cycles and insts are common to SPARC® platforms and x86 platforms, but other flavors also exist that are architecture-specific.
To see the metrics available from the experiments you have loaded, issue the metric_list command.