This is especially important for Citect Servers as they require more memory, do a lot of memory processing, and effect the performance of the entire network.

It is OK for Citect to use Virtual memory under infrequent peak loading conditions, so you should enable virtual memory. However to get good real time response you should have enough memory available.

You can tell if Citect is running out of physical memory by looking at the memory free in the Window Program manager About Dialog, and the size of you virtual memory file (in the control panel, 386 Enhances, Virtual Memory). The memory free should be greater than the size of the virtual memory file. If it is less then you should buy memory to fill the gap. For example:

If you are using a temporary swap file, the size of the virtual memory file will change with Windows needs. Because of this, the above calculation of free physical memory will be unreliable. Change to a permanent swap file and then check for free physical memory. As a permanent swap file gives better performance, you should always use a permanent swap file. The swap file should not be bigger than 8,196 Kb, because if all this virtual memory was being used, the performance of Citect would be seriously degraded.