Kbase 21726: Version 9.x Client Performance When Using Mapped Drives
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/01/2002 |
|
SUMMARY:
This Solution discusses Version 9.x client performance when the client executables reside on a mapped drive. This applies only to client executables that reside on a mapped drive; there is no performance issue when the Progress client is installed locally.
When opening a Progress client session you may find that the application is very slow to open. Once the application is open however, you find the performance improves.
EXPLANATION:
When loading and executing r-code procedures from operating system files in a directory, Progress must open and close each file individually. When loading and executing r-code procedures from a Procedure Library, Progress opens only one file, the library itself, to access all of the r-code files in the library. When you execute r-code procedures from a Procedure Library, you gain these advantages:
-- Faster access to r-code
-- Fewer file open and close operations
-- Less I/O to temporary files
This may cause a performance degradation if you choose to run the Progress client using a mapped drive.
SOLUTION:
These options that may improve performance:
If you identify which Procedure Libraries are needed for your application, you can put them at the beginning of your PROPATH. You can monitor execution environment activity by using the startup parameter -yc. Progress 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). You can then view the client.mon file with any editor. The file will show all the <filename.r> files that were accessed during the program execution. You then need to find which Procedure Library contains the .r file that was accessed. Retrieve this information by running this 4GL program:
Message search ("filename.r") view as an alert box.
This will give you the name of the procedure library that contains the .r file. Now add this Procedure Library to the beginning of your PROPATH.
If you find you are using several procedure libraries to gain access to a few .r files you can extract the .r files using prolib.exe. Then you could place these .r files in their own directory and add that directory to the beginning of the PROPATH.
These options may improve performance under some circumstances. Review the Progress Client Deployment Guide to fully understand all the options.
References to Written Documentation:
Progress Client Deployment Guide, 'Managing Client Performance' and 'Monitoring R-code Activity'