We recommend that your ClearSCADA system complies with the following operational limits:
| Parameter | 32-Bit Limit | 64-Bit Limit | Notes |
|---|---|---|---|
|
Maximum number of objects (database items) |
150,000 Objects |
1,000,000 Objects |
Exceeding these limits on 32-bit platforms will cause the ClearSCADA server to run out of virtual address space. |
|
Maximum burst rate of non-historic updates |
10,000 per second |
10,000 per second |
|
|
Maximum burst rate of historic data updates |
1,000 per second |
1,000 per second |
|
|
Maximum burst rate of alarms and events |
500 per second |
500 per second |
|
|
Maximum sustained rate of historic data updates per point |
4 per minute |
4 per minute |
Exceeding these limits will create historic files in excess of 1.3MB (the maximum recommended historic data file size for standard hardware). This limit can be exceeded provided that care is taken when selecting appropriate hardware and communication links. |
|
Maximum sustained rate of events per journal section (256 Objects) |
6,825 per hour |
6,825 per hour |
Exceeding these limits will create historic files in excess of 5MB (the maximum recommended Event Journal file size for standard hardware). This limit can be exceeded provided that care is taken when selecting appropriate hardware and communication links. |
|
Maximum number of historic files |
10,000,000 files |
50,000,000 files |
Exceeding these limits on 32-bit platforms will cause the ClearSCADA server to run out of virtual address space. |
|
Maximum number of historic data records |
6,000,000,000 records |
30,000,000,000 records |
|
|
Maximum size of a Data Table |
100MB | 100MB | If you intend creating a large number of Data Tables, also consider the Data File Cache size and the total size of all of the Data Files |
|
Maximum number of event records |
1,000,000,000 records |
5,000,000,000 records |
|
|
Maximum number of alarms |
65,000 alarms |
250,000 alarms |
|
|
Maximum number of ViewX clients |
100 |
100 |
|
| Maximum number of WebX clients | Not applicable (as the WebX server only runs on 64-bit operating systems) | 200 | |
|
Maximum number of Original WebX clients |
500 |
500 |
|
|
Maximum ClearSCADA server to ClearSCADA server link latency |
70ms |
70ms |
Exceeding this limit can result in the ClearSCADA servers being unable to synchronize correctly, server timeouts and can also cause slow performance. |
|
Minimum ClearSCADA server to ClearSCADA server link bandwidth |
Symmetrical 2 Mbit per second |
Symmetrical 2 Mbit per second |
This is the minimum ClearSCADA server-to-server bandwidth for a medium sized system, for example one with up to 5,000 points. Larger systems need correspondingly higher bandwidth and will be dependent on data update rates. |
| Minimum WebX server to ClearSCADA server link bandwidth | Not applicable (as the WebX server only runs on 64-bit operating systems) | 1 Gbit Ethernet | This limit only applies if the WebX server is installed on a separate machine to the ClearSCADA server. |
Server class computers and virtual machines (VMs) on server class computers should not be used to run ViewX in a day-to-day operational environment; instead, appropriate client machines should be used. Client machines often have a higher graphics hardware specification than server class computers. This higher graphics specification is required to run ViewX in a day-to-day operational environment, within which users might perform graphics-intensive tasks such as viewing complex Mimics, or working with multiple or floating documents
The standard graphics hardware on server class computers and on VMs on server class computers may only be adequate for running ViewX for administrative purposes (such as performing initial system configuration and user account setup).
For information on client operational limitations, please see Operational Limitations - Client.