Sizing considerations

The sizing baselines specified are based on the performance lab benchmark test results performed in BMC’s test labs. You can use these baselines for your on-premises BMC Helix IT Operations Management deployment. BMC’s performance testing is based on four different system usage profiles: compact, small, medium and large.

The following applications are hosted on a single deployment of BMC Helix IT Operations Management:

BMC Helix Continuous Optimization
BMC Helix Dashboards
BMC Helix Intelligent Automation
BMC Helix Intelligent Integrations (by using BMC Helix Developer Tools)
BMC Helix Log Analytics
BMC Helix Operations Management
BMC Helix Portal
BMC Helix Service Monitoring (BMC Helix AIOps)

Important

If you are deploying multiple containerized products such as BMC Helix Operations Management, BMC Helix Continuous Optimization, and BMC Helix IT Service Management in your environment, Contact BMC Support for the sizing guidelines.
If you are deploying BMC Helix Operations Management in a multitenant environment, contact BMC Support for the sizing guidelines.

BMC’s performance testing is based on four different system usage profiles: Compact, Small, Medium, and Large. Compact is a special sizing that is the minimum requirements for a functional BMC Helix Platform system. Compact systems are recommended only for POC systems, where resilience and system performance under load is not a consideration.

All compact systems cited on this page are non high-availability deployments for BMC Helix Operations Management and the BMC Discovery appliance. We recommend the compact sizing for a POC because it is a single-replica deployment.

If your usage exceeds the maximum numbers for the large sizing, contact BMC Support for guidance on how to size your infrastructure.

Kubernetes infrastructure sizing requirements

Compute requirements are the combined requirements of CPU, RAM, and Persistent Volume Disk requirements for the Kubernetes worker nodes. 

These compute requirements are shared between all the worker nodes in your Kubernetes cluster. The worker nodes in your Kubernetes cluster must have CPU and RAM that matches or exceeds the total infrastructure sizing requirement plus the per worker node logging requirement. This is required to support the anticipated load for the benchmark sizing category for a BMC Helix IT Operations Management deployment.

The infrastructure sizing requirement supports the following applications:

BMC Helix Continuous Optimization
BMC Helix Dashboards
BMC Helix Intelligent Automation
BMC Helix Intelligent Integrations (by using BMC Helix Developer Tools)
BMC Helix Log Analytics
BMC Helix Operations Management
BMC Helix Portal
BMC Helix Service Monitoring (BMC Helix AIOps)

Kubernetes cluster requirements

The following table represents the minimum amount of compute resources that must be available to BMC Helix IT Operations Management to function:

Note

The total sizing does not include the requirements for BMC Discovery.

Best practice
We recommend that you review the vendor documentation for sizing of control nodes. BMC does not have any specific requirements for the sizing of control nodes in a Kubernetes cluster.

For information about recommendations for canonical Kubernetes control nodes, see Considerations for large clusters in the Kubernetes documentation.

Kubernetes quotas

Quotas may be set up on the cluster namespaces to enforce requests and limits and prevent extra deployments within them. The following table are the recommended settings to allow a BMC Helix IT Operations Management deployment:

Daemon sets

Daemon sets are present in the application deployment and will have an impact on cluster requirements and quotas depending on the number of nodes in the cluster. The following table outlines the added requirements to the cluster per node in the cluster:

Kubernetes node requirements

The application must be supported with at least a certain number of worker nodes available in the cluster to operate successfully.

A worker node must have a minimum number of resources available to it for the application to make use of the worker node:

Persistent volume requirements

High performance of Kubernetes Persistent Volume Disk is essential for the overall system performance. Persistent Volume Disk requires block and NFS storage. BMC supports a Bring-Your-Own-Storage model for Kubernetes Persistent Volumes.

The following tables shows the disk requirements in GB:

We recommend that you use solid-state drive (SSD) with the following specifications:

NFS throughput and IOPS requirements: