Review Cloud Sizing Guidelines

If you plan to stand up
DX NetOps Performance Management
in the cloud, review the following cloud sizing guidelines.
If you plan to stand up
DX NetOps Performance Management
in the cloud, review the following cloud sizing guidelines. You can choose from a variety of cloud platforms, including Amazon Web Services (AWS) and Google Cloud Platform (GCP). The current guidelines focus on AWS.
Follow these steps:
  1. Determine the estimated requirements of your environment using the DX NetOps Sizing Tool.
    For more information, see the DX NetOps Sizing Tool.
  2. Review the estimated disk requirements from the sizing tool and consider your data retention rates. Your data retention rates impact disk requirements greatly.
    For more information, see Configure Data Retention Rates.
  3. Review the other entries in the sizing tool, which impact the requirements of your environment.
  4. Adjust the entries in the sizing tool until they most accurately reflect the needs of your environment.
  5. Review the guidelines for your cloud platform.
AWS
Components
Instance Types
Descriptions
Added Storage
Notes
Examples
Data Repository / Vertica
r5.4, r5.8, r5.12
r5 instance types are memory-optimized instances. These instances deliver fast performance for workloads that process large data sets in memory.
Vertica supports r5 instance types for the data repository.
For more information, see the Vertica on Amazon Web Services documentation.
The core to memory ratio best matches what the DX NetOps Sizing Tool recommends.
Storage does not factor into this recommendation. Use one of the recommended added storage options from EBS to cover the recommended disk size from the DX NetOps Sizing Tool.
IOPS SSD, Thoughput HDD
To select the instance type best suited for your data repository, review the estimated CPU requirements in the sizing tool.
The Data Repository requires storage beyond the boot disk. Amazon EBS allows you to create storage volumes and attach them to Amazon EC2 instances. Use EBS for the catalog directory and the data directory.
Using the sizing tool with the default values and 50,000 devices, the expected data repository sizing is 14 cores and 224 GiB RAM. The r5.8 has 32 hyperthreaded cores and 256 GiB RAM. You can deselect the hyperthreaded option to run at 16 cores and 256 GiB RAM, which gives the expected ratio by the sizing tool. You are not required to deselect the hyperthreaded option, as the benefit can vary from deployment to deployment.
Data Aggregator
m5.1, m5.2, m5.4
m5 instance types provide a balance of compute, memory, and networking resources.
The 1:4 CPU to memory ratio best matches the recommendations from the DX NetOps Sizing Tool.
No
To select the instance type best suited for the data aggregator, review the estimated memory requirements in the sizing tool.
Using the DX NetOps Sizing Tool with the default values and 50,000 devices, the expected data aggregator sizing is 18 cores and 48 GiB RAM. The m5.4 is the closest fitting instance type.
Data Collector
c5d.1, c5d.2, c5d4
c5 instance types are compute-optimized instances. These instances are for compute-bound applications that benefit from high performance processors.
The 1:2 CPU to memory ratio best matches the recommendations from the DX NetOps Sizing Tool.
No
To select the instance type best suited for the data collectors, consider the following guidance:
  • Select c5d.1 in a small environment monitoring around 100K items.
  • Select c5d.2 in a medium environment monitoring around 500K items.
  • Select c5d.4 in a large environment monitoring around 1000K items or an environment with intensive metrics or polling rates.
Using the DX NetOps Sizing Tool with the default values and 50,000 devices, the expected data colector sizing is 8 cores and 16 GiB RAM. The c5d.2 fits the DX NetOps Sizing Tool recommendations exactly.
NetOps Portal
MySQL Database Node
m5.1, m5.2, c5
m5 instance types provide a balance of compute, memory, and networking resources.
c5 instance types are compute-optimized instances. These instances are for compute-bound applications that benefit from high-performance processors.
IOPS SSD
To select the instance type best suited for the
NetOps Portal
MySQL database node, review the estimated memory requirements in the sizing tool.
The MySQL Database Node requires storage beyond the boot disk. Amazon EBS allows you to create storage volumes and attach them to Amazon EC2 instances. Use EBS for the MySQL data directory.
Using the DX NetOps Sizing Tool with the default values and 50,000 devices, the expected
NetOps Portal
MySQL node sizing is 12 cores and 32 GiB RAM. This example uses an m5.2. If you have a high user load, consider using a c5.4 to help with concurrent requests made by users.
NetOps Portal
Core Services Node
c5.4
c5 instance types are compute-optimized instances. These instances are for compute-bound applications that benefit from high performance processors.
No
To select the instance type best suited for the
NetOps Portal
core services node, review the estimated CPU requirements in the sizing tool.
Using the DX NetOps Sizing Tool with the default values and 50,000 devices, the expected
NetOps Portal
MySQL node sizing is 12 cores and 32 GiB RAM. This example uses an m5.2. If you have a high user load, consider using a c5.4 to help with concurrent requests made by users.
CA Virtual Network Assurance
r5.2
r5 instance types are memory-optimized instances. These instances deliver fast performance for workloads that process large data sets in memory.
DX NetOps Virtual Network Assurance
, varying based on the plugins deployed, is a memory intensive application. The r5 instance type scales best for both smaller and larger VNA deployments.
No
USe an r5.2 instance type for
DX NetOps Virtual Network Assurance
.
DX NetOps Spectrum
SS Node
c5.2, c.5.4
c5 instance types are compute-optimized instances. These instances are for compute-bound applications that benefit from high performance processors.
The 1:2 CPU to memory ratio best matches the recommendations from the DX NetOps Sizing Tool.
No
To select the instance type best suited for your
DX NetOps Spectrum
SS Node, review the estimated memory requirements in the
DX NetOps Spectrum
Sizing Tool
.
DX NetOps Spectrum
OC Node
c5.1, c5.2, c5.4
c5 instance types are compute-optimized instances. These instances are for compute-bound applications that benefit from high performance processors.
The 1:2 CPU to memory ratio best matches the recommendations from the DX NetOps Sizing Tool.
No
To select the instance type best suited for your
DX NetOps Spectrum
OC Node, review the estimated memory requirements in the Spectrum Sizer.