Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

System Sizing Guidelines

  • Last UpdatedJun 09, 2022
  • 4 minute read

The following table provides guidelines for hardware configurations suitable for System Platform 2023, based on application size. These guidelines are subject to the limitations of your Windows operating system, and if applicable, to the SQL Server edition (Express, Standard, or Enterprise). See the Technology Matrix on the AVEVA Global Customer Support website for supported versions of Windows operating systems and SQL Server.

  • An HD display is recommended for engineering tools such as the System Platform IDE.

  • A 64-bit operating system is required, regardless of system size.

  • A Windows Server operating system is required for large installations.

  • SQL Server Express is supported only for small systems, that is, installations with less than 25,000 I/O per node.

  • Pagefile.sys, the Windows paging file (also called the swap file or virtual memory file), must be enabled. The Windows default setting is enabled.

Definitions

In the table below, hardware guidelines for different types of System Platform are listed. Definitions for the terminology used in the table are:

Level (Minimum and Recommended)

Minimum level describes the baseline hardware configuration that will provide at least minimally acceptable performance for the role. Recommended level describes an expanded hardware set that provides improved performance.

Application Server Node

Application Server nodes, also called IDE nodes, are engineering workstations. These are used for creating, editing, and deploying objects.

Galaxy Repository Node

Galaxy Repository nodes, also called GR nodes, host the galaxy database once it has been deployed from an Application Server node.

Historian Server Node

Historian Server nodes host the AVEVA Historian. At its core, the Historian is essentially a Microsoft SQL database server.

Thin Client

Thin clients include include smart phones and tablets. In the context of System Platform, thin clients are platforms for web browsers and remote desktop sessions (for example, InTouch Access Anywhere clients).

Client

In the context of System Platform, clients are computers that can be used for development applications, such as remote IDE workstations, as well as for run-time applications like WindowViewer, AVEVA OMI ViewApps, and Historian Insight.

The following guidelines are provided for reference only. The system configuration required for your application will depend on multiple factors, including but not limited to the size and complexity of the application, and the features and components used.

Application

Level

Logical Processors 1

RAM 3

Free Disk Space 2, 3

Network Speed

Application Server Nodes 5

Small Application
(1 - 25,000 I/O per Node)

Minimum

4

2 GB

100 GB

100 Mbps

Recommended

8

4 GB

200 GB

1 Gbps

Medium Application
(25,000- 50,000 I/O per Node)

Minimum

8

8 GB

200 GB

1 Gbps

Recommended

16

12 GB

500 GB

1 Gbps

Large Application
(> 50,000 I/O per Node)

Minimum

16

16 GB

500 GB

1 Gbps

Recommended

32

24 GB

1 TB

Dual 1 Gbps

Galaxy Repository Nodes

Small Galaxy
(1 - 50,000 I/O per Node)

Minimum

4

2 GB

100 GB

100 Mbps

Recommended

8

4 GB

200 GB

1 Gbps

Medium Galaxy
(50,000 - 200,000 I/O per Node)

Minimum

8

8 GB

200 GB

1 Gbps

Recommended

16

12 GB

500 GB

1 Gbps

Large Galaxy
(> 200,000 I/O per Node)

Minimum

16

16 GB

500 GB

1 Gbps

Recommended

32

24 GB

1 TB

Dual 1 Gbps

Historian Server Nodes

Small Historian
(1 - 50,000 Historized Tags per Node)

Minimum

4

2 GB

100 GB

100 Mbps

Recommended

8

4 GB

200 GB

1 Gbps

Medium Application
(50,000 - 200,000 Historized Tags per Node)

Minimum

8

8 GB

200 GB

1 Gbps

Recommended

16

12 GB

500 GB

1 Gbps

Large Application
(> 200,000 Historized Tags per Node)

Minimum

16

16 GB

500 GB

1 Gbps

Recommended

32

24 GB

1 TB

Dual 1 Gbps

Thin Client Node

RDP clients, InTouch Access Anywhere browsers, mobile devices

Minimum

2

512 MB

N/A

100 Mbps

Recommended

4

2 GB

N/A

100 Mbps

Client Node

WindowViewer, ViewApp, Historian Client, Remote IDE

Minimum

4

1 GB

100 GB

100 Mbps

Recommended

8

4 GB

200 GB

1 Gbps

Remote Desktop Server Nodes

Basic RDS, InTouch Access Anywhere Server
Supports up to 15 concurrent remote sessions

Minimum

8

8 GB

200 GB

1 Gbps

Recommended

16

12 GB

500 GB

1 Gbps

Large RDS, InTouch Access Anywhere Server
Supports up to 30 concurrent remote sessions

Minimum

16

16 GB

500 GB

1 Gbps

Recommended

32

24 GB

1 TB

Dual 1 Gbps

All-In-One Node 4 (all products on a single node)

Small Application:
1,000 I/O max

Minimum

8

8 GB

200 GB

100 Mbps

Recommended

12

12 GB

500 GB

1 Gbps

Medium Application:
20,000 I/O max

Minimum

12

16 GB

500 GB

1 Gpbs

Recommended

16

32 GB

1 TB

1 Gbps

Large Application 6
100,000 I/O max

Minimum

20

32 GB

2 TB

1Gbps

Recommended

24

64 GB

4 TB

1 Gbps

1) To calculate the number of logical processors: multiply the number of physical cores by the number of threads each core can run. A four core CPU that runs two threads per core provides eight logical processors. The terms "Hyper-Threading and "simultaneous multithreading" (SMT) are also used to describe logical processors.
2) SSD drives are highly recommended.
3) In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.
4) For optimal performance of all-in-one nodes, a high clock speed (>2.8 GHz) is recommended.
5) For Application Server platform nodes, it is recommended that you deploy no more than two AppEngines per logical processor (typically one primary AppEngine and one backup).
6) For large applications on all-in-one nodes, dual XEON processors are recommended.

TitleResults for “How to create a CRG?”Also Available in