Progress
Programming
Handbook
Run-time Execution
Compile-time execution can save time in development. However, to improve application performance, the first step is to ensure that it is running in r-code form.
Thus, run-time execution has two main uses:
Application Fine Tuning and Deployment
This is the technique most often used during final construction and deployment of an end-user application. Executing an r-code file is generally much faster than compile-time executing a procedure source file. After you have completed all prototyping and testing, you might fine tune each procedure using the Application Compiler. (For more information on the Application Compiler, see the Progress Basic Development Tools (Character only) book, and in graphical interfaces, the on-line help for the Application Compiler.) You might then use the compiler to generate all the r-code files for your application and tune its final performance using database administration utilities, such as PROMON, to help establish optimum values for session startup and database connection parameters. For more information on application deployment, see the Progress Client Deployment Guide and the Progress Developer’s Toolkit.
Optimized Dynamic Code Generation
If your application includes the Progress compiler to generate and execute code dynamically, you can increase performance using the COMPILE statement. This allows you to save semi-permanent r-code files between sessions that execute much more quickly from startup. It is also a more secure way to generate dynamic code, because you can remove the procedure source files during each session, leaving only the r-code. The Application Compiler also uses this technique to compile procedures for applications. For more information on the COMPILE statement, see the Progress Language Reference .
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |