Progress
Client Deployment
Guide


Monitoring R-code Activity

You can monitor execution environment activity by using the startup parameters listed in Table 4–3 to collect usage statistics during a Progress client session.

Table 4–3: Startup Parameters for Monitoring R-code Activity 
Startup Parameter
Description
Statistics (-y)
Collects procedure access and usage statistics throughout the Progress session and writes them to an output file (by default, client.mon in your current working directory). Use the SHOW-STATS statement at any time during the session to instruct Progress to write the statistics immediately.
Statistics with CTRL-C (-yc)
Collects the same statistics as the -y parameter, but lets you press CTRL-C as an alternative to executing the SHOW-STATS statement. Use this parameter if you cannot execute SHOW-STATS.
Segment Statistics (-yd)
Collects r-code segment statistics and writes them to the client monitor file (by default, client.mon in your current working directory). It provides a breakdown of an r-code file by segment type, including the number of segments and its size. It also summarizes read and write access to the sort file by segment type and access type, including the number of times the sort file was accessed and the number of bytes read from or written to the sort file.
Statistics with Cross-reference (-yx)
Collects procedure call statistics and writes them to an output file (by default, proc.mon in your current working directory). Use this parameter to answer these questions:
  • How many calls were made in a given period of time?
  • How long did a procedure spend executing?
  • How often was a procedure swapped to and from the sort file?

For more information about these startup parameters, see the Progress Startup Command and Parameter Reference.

Interpreting R-code Usage Statistics

Figure 4–1 shows a sample excerpt from the output of the Statistics (-y) startup parameter.

Figure 4–1: Sample Statistics (-y) Output

The Reads from temp file and Writes to temp file fields show the amount of swapping to and from the sort file. Segments are written to the sort file only once. Once swapped, they remain in the sort file, even when they are reloaded into memory. For this reason, the number of writes is typically much smaller than the number of reads. If these numbers are relatively high, consider putting the sort files on a dedicated disk. For more information, see the "Temporary File I/O" section later in this chapter.

The R-code Execution Buffer field shows the current size of the execution buffer, the peak usage during the session, and the current ceiling. Use the data in these fields to determine the optimal initial ceiling for the execution buffer (that is, the point at which Progress starts swapping to the sort file). Set this value with the Maximum Memory (-mmax) startup parameter. For more information, see the "Tuning R-code Execution" section earlier in this chapter.

Interpreting R-code Segment Statistics

Figure 4–2 shows a sample excerpt from the output of the Segment Statistics (-yd) startup parameter.

Figure 4–2: Sample Segment Statistics (-yd) Output

The Per procedure temp file access statistics fields show the swap rates for each segment of each procedure executed during the session. The Per procedure segment information fields show the number and size of r-code segments in each procedure. Use this information to determine how your application design is affecting r-code performance. For more information about application design and r-code performance, see the Progress Programming Handbook.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095