Go to main content
Oracle® Developer Studio 12.6: Performance Analyzer

Exit Print View

Updated: June 2017

Output Options

These options control aspects of the experiment produced by the Collector.

Set Experiment Name with -o experiment-name

Use experiment-name as the name of the experiment to be recorded. The experiment-name string must end in the string “.er”; if not, the collect utility prints an error message and exits.

If you do not specify the –o option, give the experiment a name of the form stem.n.er, where stem is a string, and n is a number. If you have specified a group name with the –g option, set stem to the group name without the .erg suffix. If you have not specified a group name, set stem to the string test.

If you are invoking the collect command from one of the commands used to run MPI jobs, for example, mpirun, but without the –M MPI-version option and the –o option, take the value of n used in the name from the environment variable used to define the MPI rank of that process. Otherwise, set n to one greater than the highest integer currently in use.

If the name is not specified in the form stem.n.er and the given name is in use, an error message is displayed and the experiment is not run. If the name is of the form stem.n.er and the name supplied is in use, the experiment is recorded under a name corresponding to one greater than the highest value of n that is currently in use. A warning is displayed if the name is changed.

Set Directory of Experiment with -d directory-name

Place the experiment in directory directory-name. This option only applies to individual experiments and not to experiment groups. If the directory does not exist, the collect utility prints an error message and exits. If a group is specified with the -g option, the group file is also written to directory-name.

For the lightest-weight data collection,recording data to a local file is best, using the –d option to specify a directory in which to put the data. However, for MPI experiments on a cluster, the founder experiment must be available at the same path for all processes to have all data recorded into the founder experiment.

Experiments written to long-latency file systems are especially problematic and might progress very slowly, especially if Sample data is collected (–S on option, the default). If you must record over a long-latency connection, disable Sample data.

Create Experiment in a Group with -g group-name

Make the experiment part of experiment group group-name. If group-name does not end in .erg, the collect utility prints an error message and exits. If the group exists, the experiment is added to it. If group-name is not an absolute path, the experiment group is placed in the directory directory-name if a directory has been specified with -d., Otherwise, it is placed in the current directory.

Archive Load Objects in Experiment with the -A option

Control whether load objects used by the target process should be archived or copied into the recorded experiment. The allowed values of option are:

  • on – Copy load objects (the target and any shared objects it uses) into the experiment. Also copy any .anc files and .o files that have Stabs or DWARF debugging information that is not in the load object. This is the default.

  • src–In addition to copying load objects as in -A on, copy into the experiment all source files and .anc files that can be found.

  • used[src]–In addition to copying load objects as in -A on, copy into the experiment all source files and .anc files that are referenced in the recorded data and can be found.

  • off – Do not copy or archive load objects into the experiment.

If you expect to copy experiments to a different machine, or to read the experiments from a different machine, specify -A on. The experiment will use more disk space but allows the experiment to be read on other machines.

-A on does not copy any source files or object (.o) files into the experiment. You must ensure that those files are accessible from the machine on which you are examining the experiment. The files should not be changed or rebuilt after the experiment was recorded.

Archiving of an experiment at collection time, especially for experiments with many descendant processes, can be very expensive. A better strategy for such an experiment is to collect the data with -A off, and then run er_archive with the –A flag after the run is terminated.

The default setting for –A is on.

Save the Command Output to a File with -O file

Append all output from collect itself to the named file, but do not redirect the output from the spawned target, nor from dbx (as invoked with the –P option), nor from the processes involved in recording count data (as invoked with the –c argument). If file is set to /dev/null, suppress all output from collect, including any error messages.