Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

> ## Monitoring r-code activity

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

> Table 5–3: Startup parameters for monitoring r-code activity
> Startup parameter | Description
> --- | ---
> Statistics (`-y`) | Collects procedure access and usage statistics throughout the Progress 4GL 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 OpenEdge 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 OpenEdge Deployment: Startup Command and Parameter Reference .

> ##### Interpreting r-code usage statistics

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

> Figure 5–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.

> 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 OpenEdge 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.

> ##### Interpreting r-code segment statistics

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

> Figure 5–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 Appendix B "R-code Features and Functions."

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