Rockwell Automation 1757-SWKIT3200 ProcessLogix R320.0 Installation and Upgrade Guide - Manual (Page 247)

Publication 1757-IN032B-EN-P - April 2001
Performance and Capacity Specifications 7-7
be on the Servers. On Redundant Systems, primary application usage should be on
the Backup Server.
4. These applications are more for configuration and typically are not run all the time.
They represent a one-time memory allocation when running. When considering
additional RAM requirements, you should only include those applications in which
you intend to run on a daily or constant basis.
5. The Station application affects the Station and Server Node. The memory should be
added on both physical boxes per application. For example, if the Server is going to
support 5 Stations, then you would require an additional 25 MB (5 x 5).
6. RSBatch includes multiple NT services and applications.
7. These upgrade requirements are per Server Node.
8. If NIFB is run on the Primary ProcessLogix Server or the Server is Non-Redundant,
then that server is limited to only 8 CN2FFs.
9. While using the NI FBUS Configurator, you can only monitor 1 CN2FF at one time.
This application should only be run on the Backup Server (if redundant) because it
will put an additional CPU load on the system approximately 35% higher than your
normal running state. If run on a Non-Redundant Server, you must have a higher
performance CPU configuration.
10. It is possible to exceed the single CPU processing power in some larger
configurations. Due to the larger configuration, please consider following the RAM
guidelines for an NT Server platform. Dual CPU systems are not supported. The MS
Access Jet Database engine used in R320.0 does not adequately support dual CPU
systems.
ATTENTION
!
Low memory and CPU resources can affect Server
performance in the following ways:
•
Low memory can impact CB and Station operations
such as display call-up and screen refresh.
Background applications such as RSLinx and CDA
can also be impacted. On occasion, extremely low
memory resources have caused foreground and
background applications to fail.
•
Low memory causes virtual memory to be swapped
often, which itself is a CPU intensive operation.
Therefore, low memory directly affects the amount
of available CPU resources.
•
Low CPU resources can impact communication
between Clients and Server. Although the
communication subsystem guarantees data delivery,
low CPU resources can create communication
bottlenecks that adversely affect the freshness of
data displayed.
•
Low CPU resources can impact CB operations such
as: opening charts, loading, uploading and updating
project.