Rita, the CMS Pipelines Execution Profiler

Rita reports on the CPU utilization of a pipeline complex by stage and pipeline specification. With a current enough version of Pipes, Rita also reports the highwatermark value of the virtual memory used by each stage for workareas and buffers.

To invoke Rita, just change your "PIPE" command to "RITA".

The numbers displayed by Rita are CPU utilization (in milliseconds) for each stage and pipeline, both inclusive of and exclusive of the time used by subroutine pipelines invoked by the stage or pipeline.

Detailed output is written to a disk file, and a summary is displayed on the console. The filename of Rita's output file is the first eight characters of the "name" option specified on the RITA command. The filetype is of the form RITAnnn, where nnn is the first unused sequence number.

For a more detailed discussion and many examples of using Rita to tune pipelines, see Streamlining Your Pipelines.

If a user-written pipeline stage goes into a wait state outside of the control of Pipes, the wait time will be counted as CPU time.

Pipelines added with ADDPIPE are not represented in the inclusive number for the stage that adds them (nor for any others up the calling chain).

The numbers displayed by Rita do not include the CPU utilization of other pipeline sets started with PIPE commands or "runpipe" stages from within the pipeline set Rita is measuring.

Rita produces the best results when all CALLPIPEs and ADDPIPEs have the "name" option specified and when any specifications that have the same name are identical to one another.

To use Rita with a pipeline that contains a "ldrtbls" stage, NUCXLOAD RITA MODULE so that invoking Rita doesn't alter the loader tables.

Rita is much less expensive to use if RITA REXX has been compiled.

If you receive any of the following messages when you invoke Rita, you need a more current version of Pipes:

Rita requires CMS 6 or later and at least level 1.0107 of CMS Pipelines. (This is the version distributed in VM/ESA Release 2.1 (CMS 10) and in VM/ESA 370 Feature Release 1.5. These two ESA levels report their CMS Pipelines levels as 2.0201 and 1.0501 respectively.)


Melinda Varian / Office of Computing and Information Technology / Princeton University / melinda.varian@me.com
September 24, 1997