Hardware for Small Aternity Deployment (up to 30,000 devices)

Use this deployment for small production environments of Aternity to support up to 30,000 monitored devices or virtual desktops, where up to 27,000 of them are physical devices and 3,000 are virtual application sessions. It assumes 10 Aternity logged in users updating dashboards and performing in total up to 10 clicks per minute.

Small Aternity deployment

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.

Hardware Specifications for Small Deployment

The small deployment requires the following hardware specifications:

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

Aternity Management Server (which includes the Data Warehouse Server)

At least 14GB

Xeon E5 family

4 cores

2.4 GHz


JVM heap size: (learn more)



ActiveMQ JVM Heap Size: 1G

Aternity Aggregation Server


Xeon E3 family, 2 cores at 2.4 GHz


JVM heap size: (learn more)



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


Xeon E3 Family

4 Cores

2.4 GHz


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

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

Program Global Area (PGA): 2GB

Aternity Vertica Database Server


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

Xeon E5 family

8 Cores

2.4-3.6 GHz

15MB CPU cache

200GB (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.

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


Xeon E5 family

6 Cores

2.4-3.6 GHz


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 100GB

  • <kafka>: at least 20GB

If there is no need for optional components, you can reduce 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.

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.