MAINPM User's Guide, Chapter 1

previous   next   top   contents   index   framed top   this page unframed


1. Introduction

Medium- to large-scale software products are usually developed in several stages. All but the last stage are concerned with the software's correctness. The last stage involves improving the software's performance once the software appears to be correct. A typical program spends most of its time in a relatively small part of its code, but the program's author(s) may have little or no idea where that small amount of code is. Thus, they run the risk of making performance improvements in the “wrong” areas of the program, so that the improvements have little effect on the performance of the program as a whole. MAINPM helps focus attention on those parts of the program in which performance improvements would be most effective.

MAINPM can report to the user several aspects of a MAINSAIL program's performance:

Some of the above statistics can be reported in more than one way:

MAINPM can also list the PROCEDUREs or statements that were not executed when a program was run.

Resources used may be CPU time, wall clock time, chunk (dynamic object) space usage, STRING space usage, static space usage, or a user-defined quantity. CPU time information is available only on systems that provide access to a system clock. User-defined resource measurement is described in detail in Chapter 6.

1.1. Version

This version of the MAINPM User's Guide is current as of the proposed Version 16.30.1 of MAINSAIL (which has not yet been released).

This document is preliminary. Its contents have been updated to include information about the proposed 16.30.1 release, but the document has not been thoroughly proofread. Please contact XIDAK if you have any questions concerning this document or if you find any errors in it.

previous   next   top   contents   index   framed top   this page unframed

MAINPM User's Guide, Chapter 1