Aternity on-premise supports a wide range of deployments with different hardware sizing and network layouts, depending on the number of devices you intend to monitor for performance:

Always use a dedicated PC for the Database Server and another dedicated PC for the Dashboard Server.

You can add more components on the Management Server PC for smaller deployments:

• (Trial demo deployments less than 100 devices) The Management Server PC can also have the Database Server, Analytics Server, Data Warehouse Server, and Aggregation Server, all on the same PC.

• (Small deployments less than 3,000 devices) The Database Server is standalone. The Management Server PC has ALL the following: the Analytics Server, Data Warehouse Server, and Aggregation Server.

• (Mid-sized deployments less than 25,000 devices) The standalone servers are: Database Server and Aggregation Server. The Management Server PC has ALL the following: Analytics Server and Data Warehouse Server.

• (Larger deployments above 25,000 devices) The standalone servers are: Database Server, Data Warehouse Server and Aggregation Server. The Management Server PC should only have the Analytics Server.

The supported deployment sizes are:

• Trial Aternity deployments (up to 100 devices)

• Small Aternity deployments (up to 3000 devices)

• Medium Aternity deployments (up to 25,000 devices)

• Large Aternity deployments (up to 75,000 devices)

• Very large Aternity deployments (up to 100,000 devices)

• Extra large Aternity deployments (up to 150,000 devices)

Separate from sizing, you must also choose the network topology for your deployment by determining where to place each of the components in the network. Aternity supports three types of deployment topologies: local, centralized or distributed.

Based on the likely frequency of data reporting, you can assign the hardware sizing and deployment type:

Where:

• # devices and VDIs is the maximum number of monitored physical devices and virtual desktop VDIs (not their hypervisors) which report their performance to Aternity at the same time.

• # virtual sessions is the maximum number of monitored virtual application sessions reporting their performance to Aternity at the same time.

  # virtual servers is the maximum number of virtual application servers (like Citrix XenApp) or RDP servers, which generate the monitored virtual sessions.

• PRC is the average number of PRC monitors per device, averaged over 24 hours. By default, devices report PRC once an hour.

• AR/min is the maximum number of activity response times reported per device per minute at peak times. There are two types:

  • WPM AR/min is the average number of activities reported which were defined in Page Load Activities (WPM) for managed web applications per device per minute.

  • Non-WPM AR/min is the average number of all other activities reported per device per minute (including desktop applications, monitored mobile apps, and custom activities for web applications).

• Discovery AR/min The average number of applications which are actively in use simultaneously on a device per minute, which report discovery data (like usage time, wait time and UXI).

• Aternity users The number of simultaneous users accessing the dashboards and administration features of Aternity.