Profiling Your 4GL Application
To profile a 4GL application, you run the 4GL application with profiling enabled.
As the 4GL Client exits and returns to the operating system, it produces an output file
containing a summary of what code was executed and timing data for each line that was
executed. (prof.out is the default file name)
We often refer to the data in that output file as representing a “profiling session”.
Then you use the Profiling Viewer to import that summary data
into a Progress database;
the Profiling Tool does an analysis of the data as part of the
import process, and then
the profiling session is available for view.
Starting with version 9.0A, there is a PROFILER
system handle that may be used to
start and stop the profiling, to write the data, to
specify the output file, and to control a
host of other things associated with profiling.