Hardware for XX-Large Deployment (up to 220,000 devices)

The XX-large Aternity deployment supports up to 220,000 monitored devices or virtual desktops, where up to 200,000 of them are physical devices and 20,000 are virtual application sessions. It assumes 10 Aternity logged in users updating dashboards and performing in total up to 10 clicks per minute.

XX-large Aternity deployment
Important

Synchronize all Aternity components to have the same date, time AND time zone.

Aternity requires one Aggregation Server per 40,000 monitored devices and one Vertica Database Server node per 25,000 monitored devices. So, calculate the number of servers you need following the amount of monitored devices in your organization.

Data Warehouse Server should be deployed on a dedicated machine separately from other Aternity servers in deployments with more than 40,000 monitored devices.

The disk space is for each separate Vertica Database Server node in a cluster, before any high availability (k-safety = 0). For minimum high availability, we recommend k-safety = 1 (learn more).

Hardware Specifications for XX-Large Deployments

The XX-large deployment requires the following hardware specifications:

Component Minimum Memory (RAM) Minimum CPU Minimum free disk space Additional configuration

6 x Aternity Aggregation Server

12GB

Xeon E3 family, 2 cores at 2.4 GHz

30GB

JVM heap size: (learn more)

-Xmx8192m

-XX:MaxNewSize=4096m

Aternity Management Server

At least 24GB

Xeon E5 family

16 cores

2.4-3.6 GHz

80GB

JVM heap size: (learn more)

-Xmx18432m

-XX:MaxNewSize=8192m

ActiveMQ JVM Heap Size: 2G

Aternity Data Warehouse Server

At least 26GB

Xeon E5 family

16 cores

2.4 GHz

350GB

You need disk storage of 1.5GB for each 1000 monitored devices for seven days data retention.

JVM heap size: (learn more)

-Xmx22528m

-XX:MaxNewSize=10240m

Aternity Dashboard Server

64GB

Add 16GB RAM for each additional 10 logged users.

Xeon E5 family

24 Cores

2.4-3.6 GHz

15MB CPU cache

Add 8 cores for each additional 10 logged users.

100GB (SSD)

Or I/O per sec (IOPS): 900

For less standard hardware configurations, see the setup instructions and hardware best practices from Tableau. To deploy on a virtual machine, you must guarantee the CPU and memory requirements.

Aternity Oracle Database Server

64GB

Xeon E5 Family

16 Cores

2.4 GHz

1.6TB

I/O per sec (IOPS): At least 1200

Oracle's System Global Area (SGA): 40GB

Program Global Area (PGA): 14GB

9 x Aternity Vertica Database Server

32GB

Add 16-32 GB RAM for each additional 10 logged users.

Xeon E5 family

16 Cores

2.4-3.6 GHz

15MB CPU cache

400GB (SSD) for each node

Vertica Database Server setup checks that free disk space meets the hardware requirements. In deployments with maximum two nodes, the setup checks that free disk space is at least 200GB per node. In deployments with three nodes and above, the setup automatically configures high availability and checks that free disk space is at least 400GB per node.

The disk space is for each separate Vertica Database Server node in a cluster, before any high availability (k-safety = 0). For minimum high availability, we recommend k-safety = 1 (learn more).

If you deploy on virtual machines, you MUST define all resources as dedicated or reserved (Resource Allocation > Reservation). In addition, you can use a Logical Volume Manager (LVM) in Aternity 11 on any hard drive with no restrictions. See Vertica limitations for LVM.

Verify that the disk partition dedicated to the Vertica data folder (Target directory) uses the EXT4 file system. Enter df -Th to verify.

Aternity Docker Components Server

42GB

Xeon E5 family

18 Cores

2.4-3.6 GHz

850GB

20GB for partition with Docker engine’s local storage, by default located at /var/lib/docker/.

Divide free disk space into several partitions where each partition is dedicated to the data directory of a different component: Messaging Broker(Kafka), and Raw Data Component (Cassandra). Allocate disk space to each partition according to hardware requirements of the relevant sizing model. The rest free disk space is dedicated to log files and REST APIs.

<cassandra>: at least 500GB

<kafka>: at least 80GB

If there is no need for optional components, you can reduce 7GB of memory and 3 CPU cores.

If you do not deploy Aternity Data Source for Portal, you can reduce the amount of memory by 2GB and CPU cores by 0.5.

If you do not deploy Aternity REST API Server, you can reduce the amount of memory by 2GB and CPU cores by 0.5.

You must also install each server with the required operating system and other software. For details, see the system and software requirements for each server.