Oracle® Solaris Studio 12.4: Performance Analyzer

Exit Print View

Updated: January 2015

Experiment Names

The default name for a new experiment is . The suffix .er is mandatory: if you provide a name without this suffix, an error message is displayed and the name is not accepted.

If you choose a name with the format, where n is a positive integer, the Collector automatically increments n by one in the names of subsequent experiments. For example, is followed by, , and so on. The Collector also increments n if the experiment already exists, and continues to increment n until it finds an experiment name that is not in use. If the experiment name does not contain n and the experiment exists, the Collector prints an error message.

Subexperiments follow similar naming rules. See Subexperiments for more information.

Experiment Groups

Experiments can be collected into groups. The group is defined in an experiment group file, which is stored by default in the current directory. The experiment group file is a plain text file with a special header line and an experiment name on each subsequent line. The default name for an experiment group file is test.erg. If the name does not end in .erg, an error is displayed and the name is not accepted. Once you have created an experiment group, any experiments you run with that group name are added to the group.

To manually create an experiment group file, create a plain text file whose first line is as follows:

#analyzer experiment group

Then add the names of the experiments on subsequent lines. The file extension must be.erg.

You can also create an experiment group by using the –g argument to the collect command.

Experiments for Descendant Processes

Experiments for descendant processes are named with their lineage as follows. To form the experiment name for a descendant process, an underscore, a code letter, and a number are added to the stem of its creator’s experiment name. The code letter is f for a fork, x for an exec, and c for combination. The number is the index of the fork or exec (whether successful or not). For example, if the experiment name for the founder process is, the experiment for the child process created by the third call to fork is . If that child process calls exec successfully, the experiment name for the new descendant process is

Experiments for MPI Programs

Data for MPI programs are collected by default into, and all the data from the MPI processes are collected into subexperiments, one per rank. The Collector uses the MPI rank to construct a subexperiment name with the form, where m is the MPI rank. For example, MPI rank 1 would have its experiment data recorded in the directory.

Experiments on the Kernel and User Processes

Experiments on the kernel by default are named rather than When data is also collected on user processes, the kernel experiment contains subexperiments for each user process being followed.

The subexperiments are named using the format For example an experiment run on a sshd process running under process ID 1264 would be named