iFIX provides you with a performance-oriented picture development tool that is open and easy to use. Because it is an event-driven system, iFIX does not allocate memory or use processor speed when it is not necessary. When an event occurs, only then does the system access the CPU. This makes the drawing environment of iFIX more efficient. You can draw a shape and link it to a live I/O source in a matter of seconds. And, using the design considerations outlined in the previous section, you can save even more time in your development and implementation.
Still, external to iFIX software, there are some guidelines that you should abide by to make iFIX perform more effectively for your specific needs.
The two easiest ways to optimize the performance of your pictures are to make your pictures open faster and update faster. Common to both attributes are:
Processor Speed – The faster the machine's processor, the faster your applications perform.
RAM – To avoid disk swapping, your computer must have enough memory to contain all applications, databases, and cached pictures. If the computer does not have enough memory, Windows swaps the applications to disk.
To optimize the speed at which iFIX initially displays pictures, iFIX includes a Resolve feature, described in the Resolving Pictures section that follows. To further optimize the speed at which your pictures are dynamically updated based on changes in process conditions, try doing one or more of the following:
- Use computers that have a local bus video.
- Update to a faster graphics card, if necessary.
- Avoid blinking alarms. For more information, refer to the Blinking Alarms section.
- Use exception-based processing in your database.
- Change the refresh rate. For more information, refer to the Increasing the Refresh Rate section in the Setting up the Environment manual.
