next up previous
Next: Limitations of the resource logging
Up: Interpretation of results
Previous: Interpretation of results

Structure of the output file

 

As it runs, the logging process will append to a log file (by default ccdbig_time.log). Initially a header will be written indicating some of the operating parameters and details of the machine which is being run on. One subsequent line will be written for each program as it is run, giving the size of the image, the number of objects in the data frame, the name of the application being run, the CPU time and elapsed time in seconds, the maximum total (virtual memory) size and maximum resident (real memory) size of the process in kilobytes, and the remaining disk space. A section of a log file could therefore look something like this:

                            Elapsed(s)   CPU(s)   RSS(k)  Size(k) Diskfree(M)
SunOS cass58 5.6 Generic sun4u sparc SUNW,Ultra-1
 10:32am  up 19 day(s), 22:21,  0 users,  load average: 0.04, 0.14, 0.12
Tue Jul  7 10:32:57 BST 1998
714     /data/cass58a/mbt/scratch
 
Variance:           FALSE
Keepard:            FALSE 
Biasframe:          TRUE
Normalisation:      TRUE
Data type:          _REAL
Logging interval:   15

Pixels Objects     Command
                            Elapsed(s)   CPU(s)   RSS(k)  Size(k) Diskfree(M)
   3000   1012     ccdbgen:        403      349    39024    42024        2910
   3000   1012     display:          3        2    19496    45984        2910
   3000   1012    makebias:         43       36    39440    42840        2879
   3000   1012      debias:        593       54   174208   179784        2715
   3000   1012     display:         17        2    14664    41944        2715
   3000   1012    makeflat:        179       60    92384   101632        2635
   3000   1012     ardmask:          6        3    94800   135424         140
   3000   1012     flatcor:         17        4    89032   101616        2635
   3000   1012     findobj:         25       16    35944    42760        2635
   3000   1012     tranndf:        187      167    95568   105360        2600
   3000   1012 makemosnorm:        600      515    51704    59256        2567
   3000   1012  makmoscomb:         47        7     4920    12128        2546

The meanings of the values logged are as follows:



next up previous
Next: Limitations of the resource logging
Up: Interpretation of results
Previous: Interpretation of results

CCDBIG: assessing CCDPACK resource usage for large data sets
Starlink System Note 69
Mark Taylor
6 July 1998
E-mail:ussc@star.rl.ac.uk