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)


Important

  • If you use a combination of some of the products such as BMC Helix Operations Management, BMC Helix Continuous Optimization, and BMC Helix IT Service Management in your environment, contact BMC Support Open link for the sizing guidelines.
  • If you are deploying BMC Helix Operations Management in a multitenant environment, contact BMC Support Open link for specific sizing guidelines.

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 Open link for guidance on how to size your infrastructure.

ParametersCompact (POC)SmallMediumLargeExtra large

Total number of devices.
Includes PATROL Agents and/or custom devices.

Important: Make sure that you do not exceed the number of MI (Monitored instances) per device. 

100


3,000


7,500


15,000


60,000


Monitored instances (Other sources, such as Prometheus and Rest API)1000100,000250,000500,0001,500,000
Number of MI per device1033333325
Monitored attributes (Other sources, such as Prometheus and Rest API)10,000600,0001,500,0003,000,00010,000,000
Number of Attributes per device100200200200167
Events per day (Alarm, Anomalies and External Events)5,00030,00075,0001,500,0005,000,000
Configuration policies1001,0001,50010,00020,000
Number of policies per device12211
Number of groups up to501,5002,5004,5006,000
Number of concurrent users550100150200
BMC Helix AIOps
Services255001,0003,0007,500
Situations103005001,0002,000

BMC Helix Continuous Optimization

Ingestion of samples per day in million50 mil50 mil100 mil500 mil750 mil
BMC Helix Log Analytics
Log ingestion per day500MB30GB100GB250GB1TB
Number of Logstash151050100
Number of days for retention33333

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:

CategoryCPU (Core)RAM (GB)
Compact33197
Small88363
Medium145430
Large210876
Extra large3301024

Important

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. We do 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 Open link 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 lists the recommended settings to deploy BMC Helix IT Operations Management: 

BMC Helix Platform namespace quotas

CategoryCPU requests (Millicore) CPU limits (Millicore) MEM requests (GB) MEM limits (GB) 
Compact

33,000 

196,000

124

385

Small

92,000 

345,400

312

683

Medium

145,000 

534,600

416

1157

Large

221,000 

776,600 

659

1746

Extra large

334,000 

1,089,000

913

2454

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: 

Deployment Size 

Minimum worker nodes available 

Minimum available CPU (cores) in worker node 

Minimum available memory (GB) in worker node 

Compact 

4 

12 

16 

Small 

4 

12 

16 

Medium 

6 

14 

22 

Large 

6 

16 

32 

Extra large

6

16

32

Persistent volume requirements

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 model for Kubernetes Persistent Volumes.

The following tables shows the disk requirements in GB: 

Block Storage (GB)

Compact 

Small 

Medium 

Large 

Extra large

1,739

3,372 

5,982 

13,742 

15266

RWM (GB)

Compact 

Small 

Medium 

Large 

Extra large

91 

91 

91 

91 

91

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

Specification 

Compact 

Small 

Medium 

Large 

Extra large

Average latency 

< 100ms 

< 100ms 

< 100ms

< 100ms

< 100ms

Write throughput 

20 MB/s 

150 MB/s 

165 MB/s 

200 MB/s 

200 MB/s 

Read throughput 

100 MB/s 

800 MB/s 

1 GB/s 

1.2 GB/s 

1.2 GB/s 

IOPS Write 

1K 

3K 

3.2K 

3.5K 

3.5K 

IOPS Read 

3K 

10K 

11K 

12K 

12K 

RWM throughput and IOPS requirements: 

Specification 

Value 

Read throughput 

10 MBPS 

Write throughput 

5 MBPS 

IOPS Read 

3K 

IOPS Write 

1K 

Sizing guidelines for the BMC Discovery appliance

CategoryCPURAM (GB)Disk (GB)Number of servers per environment
Compact (not in high availability)241001
Small483003
Medium8165003
Large8641TB5
Extra large8641TB5

Was this page helpful? Yes No Submitting... Thank you

Comments