How does PROFILER determine the statement execution times that it reports?
The PROFILER Assembler Module is given control by NATURAL at the start of each statement execution. At that time, PROFILER makes a note of the library, program, and statement number being executed. PROFILER also checks the CPU timer and determines how long it took to execute the previous statement, subtracting a small amount to compensate for the product’s own overhead. If the statement is a database-accessing statement (e.g., FIND or READ), PROFILER makes a note of the time that elapses from the point at which the call was issued to the database and the point at which NATURAL receives the response from the database. The statistics are periodically written to an ADABAS file for later reporting by PROFILER.