Large system topology elements
- Last UpdatedAug 13, 2025
- 1 minute read
The following elements and data is derived from extensive product testing in lab environments. The I/O data is based on simulated I/O.
The following elements and data is derived from single Unit Applications (the Unit application table):
|
Platforms - Peer-to-Peer AutomationObject Server/Visualization node |
40 |
|
Platforms - Galaxy Repository Server |
1 |
|
IndustrialSQL Server Historian Server Node |
1 |
|
Object Instances per Galaxy |
20,000 (40 nodes x 500 total object instances) |
|
Object Instances per Platform |
509 (includes platform, areas, engines, etc.) |
|
Total I/O per Galaxy |
34,224 (~ 36,000 or 900 Unit Application I/O points x 40) |
|
I/O Points per Server Platform |
900 |
|
Inputs |
300 changes/sec |
|
Outputs |
10 changes/sec |
|
History stores |
300 changes/sec |
|
Steady state new alarm arrival |
3/sec |
|
Alarm bursts of limited duration |
2000/sec |
Note: Attribute tuning for Redundant AppEngines is described on "Tuning Redundant Engine Attributes" on page 87.
In steady-state condition the system performed as described in the following table:
|
Node |
CPU |
Memory (MB) |
Network Usage @ 100 MB |
|
GR |
5% |
700 |
0.3% |
|
Historian |
20% |
563 |
0.3% |
|
AutomationObject Server/Visualization Node |
60% (1.9 GHz PC) 40% (2.4 GHz PC) |
460 (Average) |
0.7% (Win 2003) 0.68% (Win XP Pro) |