There are a few ways to speed up linking programs with WL32 as well as to increase the operational efficiency of your CauseWay applications.


Almost without exception, the best way to increase runtime performance of all CauseWay applications is to ensure that physical memory is large enough to meet all of the program's needs. Performance suffers when CauseWay creates a temporary file for virtual memory, swapping 4K blocks of the program's code and data to and from disk. Naturally this may not be possible in all cases, but it is a worthy goal. Generally the more physical memory, even when virtual memory is being used, the better an application's performance.

When using a disk cache program, be sure not to use too much extended memory. Although a disk cache program is beneficial, allocating it too much memory can deprive CauseWay of required extended memory and can degrade application performance.

If your program uses virtual memory, CauseWay's VMM creates a temporary swap file. If you have more than one disk drive, then you may wish to direct creation of the swap file to the faster disk drive on your system using the CauseWay=SWAP TEMP or TMP environment variables. Do not create a RAM disk if this will lower your physical memory because this is less efficient than allowing CauseWay to use physical memory itself.

Remember that virtual memory is part of total memory when using CauseWay. If your default drive, or the drive pointed to by the TEMP or TMP environment variables has little free space, this will be reflected in total memory available to the CauseWay application. If disk free space is less than physical memory, then CauseWay shuts off all use of virtual memory. Windows and OS/2 handle virtual memory internally and supply it through the swap file and DPMI settings for the application.

Next Page

Previous Page

Go to Table of Contents

Go back to Devore Software & Consulting home page