Naming Convention for Descendant Experiments

Descendant experiments are named as follows:

For example, if the experiment name for the initial process is test.1.er, the experiment for the descendant process created by its third fork is test.1.er/_f3.er. If that descendant process execs a new image, the corresponding experiment name is test.1.er/_f3_x1.er.

You can prepare an experiment group file with the explicit names of descendant experiments of interest.

To examine descendant processes in the Analyzer, load the founder experiment and choose View and choose Filter Data. The Analyzer displays a list of experiments with only the founder experiment checked. Uncheck the founder experiment and check the descendant experiment of interest.

See also
Analyzing Performance Data
Collecting Performance Data on a Running Process
Collecting Performance Data Using the Performance Tools Collect Windows
Opening, Adding, and Dropping Experiments

Can't find what you are looking for? Submit your comments at http://www.sun.com/hwdocs/feedback.
Legal Notices