Sizing and scalability 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.
The following applications were tested in the BMC test labs for BMC Helix IT Operations Management sizing considerations:
- BMC Helix Continuous Optimization
- BMC Helix Dashboards
- BMC Helix Intelligent Automation
- BMC Helix Developer Tools
- BMC Helix Log Analytics
- BMC Helix Operations Management
- BMC Helix Portal
- BMC Helix Service Monitoring (BMC Helix AIOps)
BMC’s performance testing is based on five different system usage profiles: compact, small, medium, large, and extra large.
The compact is a special sizing that is the minimum requirement 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. We recommend the compact sizing for a POC because it is a single-replica deployment.
If your usage exceeds the maximum numbers for the extra 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:
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 lists the recommended settings to deploy BMC Helix IT Operations Management:
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:
Worker node disk requirements
Kubernetes worker nodes require the following free disk space allocation for container images:
Requirement | Value |
|---|---|
Worker node system disk | At least 100 GB |
Persistent volume requirements
The high performance of Kubernetes Persistent Volume Disk is essential for the overall system performance. Persistent Volume Disk requires block and Read Write Many (RWM) storage; for example, CephRBD and NFS. We support a Bring-Your-Own-Storage class for Kubernetes persistent volumes.
The following tables show the disk requirements in GB:
We recommend that you use solid-state drive (SSD) with the following specifications:
RWM throughput and IOPS requirements:
Sizing guidelines for the BMC Discovery appliance