The following table lists the recommended Geo SCADA Expert server configurations for a variety of client and server scenarios (with Read performance being one of the most significant requirements).
In the table, the term ‘object’ refers to a database item whereas ‘point’ refers to a specific type of database item that stores I/O (a database point). Historic points are database points that have the
| Application | Server Requirement (minimum configuration) |
|---|---|
|
Small stand-alone client-server with up to 10,000 objects and 1-2 remote clients |
4 cores, 8GB RAM, 50GB free disk space. Desktop class (rather than server class) hardware and operating system. For the server installations, use computers that are running a suitable 64-bit operating system (see 64-Bit). |
|
Server with 10,000 objects, 5,000 historic points stored for 2 years online, 3 or more clients |
4 cores, 8GB RAM, 25GB free space on high performance disks for database configuration, log files, and so on. A separate 250GB high performance disk system for historic data. Server class hardware and 64-bit operating system. |
|
Server with 50,000 objects, 25,000 historic points stored for 2 years online, multiple clients |
4 cores, 8GB RAM, 25GB free space on high performance disks for database configuration, log files, and so on. A separate 500GB high performance disk system for historic data. Server class hardware and 64-bit operating system. |
|
Server with 100,000 objects, 75,000 historic points stored for 2 years online, multiple clients |
4 cores, 16GB RAM, 50GB free space on high performance disks for database configuration, log files, and so on. A separate 1TB high performance disk system for historic data. Server class hardware and 64-bit operating system. |
|
Server with 175,000 objects, 100,000 historic points stored for 2 years online, multiple clients |
4 cores, 16GB RAM, 50GB free space on high performance disks for database configuration, log files, and so on. A separate 2TB high performance disk system for historic data. Server class hardware and 64-bit operating system. |
|
Server with 250,000 objects, 150,000 historic points stored for 2 years online, multiple clients |
8 cores, 32GB RAM, 100GB free space on high performance disks for database configuration, log files, and so on. A separate 4TB high performance disk system for historic data. Server class hardware and 64-bit operating system. |
|
Server with 450,000 objects, 250,000 historic points stored for 2 years online, multiple clients |
8 cores, 48GB RAM, 100GB free space on high performance disks for operating system, installed applications, database configuration, and so on. A separate 50GB high performance disk system for log files. A separate 4TB high performance disk system for Historic data. A separate 4TB high performance disk system for Event Journal data. Server class hardware and 64-bit operating system. |
|
Server with 1,000,000 objects, 500,000 historic points stored for 2 years online, multiple clients |
16 cores, 96GB RAM, 100GB free space on high performance disks for operating system, installed applications, database configuration, and so on. A separate 100GB high performance disk system for log files. A separate 8TB high performance disk system for Historic data. A separate 8TB high performance disk system for Event Journal data. Server class hardware and 64-bit operating system. |
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).
There are many factors that can affect disk space use, including the amount of historic data your system generates and the overheads and mechanics of the file system. In many cases, you can calculate a suitable disk size by following these steps:
- Estimate the approximate number of historic and event records that you expect your Geo SCADA Expert system to generate over a year. Each historic record is 32 bytes and each Event Journal record is 768 bytes.
- To allow for overheads such as clusters, double the amount you estimated in step 1.
- For efficient disk usage, double the total from step 2.
- If you intend using Geo SCADA Expert's
- If you intend using Geo SCADA Expert's
This should provide you with an approximate value for the amount of disk space your system requires for a period of one year. Using this information, you can determine what size of disk you need to store a year's-worth of data. If you want to calculate the amount of disk space required to store data for a different length of time, adjust the time period accordingly in your calculations in the steps above.
With regard to the disk space required to store log files, we recommend that you calculate the amount of disk space needed to store at least 72 hours of logging (ideally longer), regardless of the size of your system. The storage required for log files will vary directly with the logging options selected and the duration of log file retention. Take care to ensure that the log files are written to a partition that contains sufficient disk space and does not impact on the space required for other files
For more information on the required desktop and server class operating systems, see Virtualization and Cloud.
For information on ViewX client recommendations, see Client PC Requirements.
The typical point to object ratio is around 1:2. So for a system with 50,000 points, this equates to around 100,000 objects. However, ratios vary per system and this should only be regarded as an estimate. Some ratios may require lower or higher specification computers, depending on the actual configuration.
Further Information
Disk architectures: Disk Drives and RAID Arrays.
For further information on PC requirements specific to your particular operating system, see the relevant system requirement pages at http://www.microsoft.com
Geo SCADA Expert System Performance Guidelines.
For further information about log files,
Virtual ViewX Server Requirements.
Virtual ViewX Server Configuration and Performance Guidelines.