Execution summary

The following example shows a sample of the execution summary.

*****************************************************************************************
splat Cmd:	splat -p -sa -da -S100 -i trace.cooked -n gensyms -o splat.out 

Trace Cmd:   trace -C all -aj 600,603,605,606,607,608,609 -T 20000000 -L 200000000 -o CONDVAR.raw    
Trace Host:  darkwing (0054451E4C00) AIX 5.2
Trace Date:  Thu Sep 27 11:26:16 2002

PURR was used to calculate CPU times.


Elapsed Real Time:        0.098167
Number of CPUs Traced:    1            (Observed):0
Cumulative CPU Time:      0.098167


                                                       start                    stop   
                                            --------------------    -------------------- 
trace interval     (absolute tics)                    967436752               969072535   
                   (relative tics)                            0                 1635783   
                   (absolute secs)                    58.057947               58.156114  
                   (relative secs)                     0.000000                0.098167  
analysis interval  (absolute tics)                    967436752               969072535   
                   (trace-relative tics)                      0                 1635783   
                   (self-relative tics)                       0                 1635783   
                   (absolute secs)                    58.057947               58.156114  
                   (trace-relative secs)               0.000000                0.098167  
                   (self-relative secs)                0.000000                0.098167  
**************************************************************************************

From the example above, you can see that the execution summary consists of the following elements:

• The splat version and build information, disclaimer, and copyright notice.
• The command used to run splat.
• The trace command used to collect the trace.
• The host on which the trace was taken.
• The date that the trace was taken.
• A sentence specifying whether the PURR register was used to calculate CPU times.
• The real-time duration of the trace, expressed in seconds.
• The maximum number of processors that were observed in the trace (the number specified in the trace conditions information, and the number specified on the splat command line).
• The cumulative processor time, equal to the duration of the trace in seconds times the number of processors that represents the total number of seconds of processor time consumed.
• A table containing the start and stop times of the trace interval, measured in tics and seconds, as absolute timestamps, from the trace records, as well as relative to the first event in the trace
• The start and stop times of the analysis interval, measured in tics and seconds, as absolute timestamps, as well as relative to the beginning of the trace interval and the beginning of the analysis interval.