Hardware for Medium Aternity Deployment (up to 60,000 devices)

The medium Aternity deployment supports up to 60,000 monitored devices or virtual desktops, where up to 54,000 of them are physical devices and 6,000 are virtual application sessions. It assumes 10 Aternity logged in users updating dashboards and performing in total up to 10 clicks per minute.

Medium 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.

Hardware Specifications for Medium Deployments

The medium deployment requires the following hardware specifications:

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

2 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 16GB

Xeon E5 family

4 cores

2.4 GHz

80GB

JVM heap size: (learn more)

-Xmx10240m

-XX:MaxNewSize=4096m

ActiveMQ JVM Heap Size: 2G

Aternity Data Warehouse Server

At least 14GB

Xeon E5 family

4 cores

2.4 GHz

100GB

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

JVM heap size: (learn more)

-Xmx10240m

-XX:MaxNewSize=4096m

Aternity Dashboard Server

32GB (you can ignore the RAM size warning during setup)

Add 16GB RAM for each additional 10 logged users.

Xeon E5 family

16 Cores

2.4-3.6 GHz

15MB CPU cache

Add 8 cores for each additional 10 logged users.

50GB (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

16GB

Xeon E5 Family

8 Cores

2.4 GHz

450GB

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

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

Program Global Area (PGA): 3GB

2 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

200GB (SSD) for each 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 (see Target directory below) uses the EXT4 file system. Enter df -Th to verify.

Aternity Docker Components Server

22GB

Xeon E5 family

8 Cores

2.4-3.6 GHz

230GB

<sda>: at least 5GB

<cassandra>: at least 150GB

<kafka>: at least 30GB

4GB of memory and 1.4 CPU cores, which is negligible in this deployment size.

In any case, we provide the detailed calculation:
  • If you do not deploy Aternity Data Source for Portal, you can reduce the amount of memory by 1GB and CPU cores by 0.2.
  • If you do not deploy Aternity REST API Server, you can reduce the amount of memory by 1GB and CPU cores by 0.2.
  • If you do not deploy SDA Server (Service Desk Alerts), you can reduce the amount of memory by 2GB and CPU cores by 1.

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.