This documentation supports an earlier version of BMC Helix IT Service Management on-premises deployment.

To view the documentation for the latest version, select 23.3.01 from the Product version picker.

Sizing and scalability considerations

The sizing baselines specified in this topic are based on the performance lab benchmark test results performed in BMC’s test labs. You may use these baselines as a reference for your on-premises BMC Helix Service Management deployment.

Important

  • The Kubernetes cluster and worker node sizing guidelines in this topic do not include BMC Helix ITSM Insights, BMC Helix Business Workflows, and BMC Helix Multi-Cloud Broker requirements.
  • The Kubernetes cluster and worker node sizing guidelines in this topic do not include the installation of BMC Helix Service Management in a multitenant BMC Helix Platform environment.
  • If you are deploying multiple containerized products such as BMC Helix Service Management, BMC Helix IT Operations Management, and BMC Helix Continuous Optimization in your environment, prepare your cluster to match the combined sizing for all products.
    For information about BMC Helix Operations Management and BMC Helix Continuous Optimization guidelines, see Sizing and scalability considerations Open link in the BMC Helix IT Operations Management deployment documentation.

BMC provides improved sizing templates for the BMC Helix Service Management 22.1.06 deployment sizes: Compact, Small, Medium, and Large. To apply these templates to your existing BMC Helix Service Management environment, see Upgrading BMC Helix Service Management to 22.1.06.

For fresh installation of BMC Helix Service Management, see Installing.

Concurrent user requirements

Sizing requirements are measured in groups of T-shirt sizes such as Small, Medium, and Large. Each group has a considered maximum load of the following users:

  • Concurrent usersrepresent the number of users who are logged in and actively working on a system across each of the following applications that are hosted on a single deployment of BMC Helix Service Management:
    • BMC Helix ITSM
    • BMC Helix ITSM: Smart IT
    • BMC Helix Dashboards
    • BMC Digital Workplace
    • BMC Digital Workplace Catalog
    • BMC Live Chat
  • Resilient concurrent usersare the maximum number of users that the deployment should handle from a single failure without service interruption if pods in the deployment become unavailable.

In real-world deployments, concurrent users might not be the only factor that drives the categorization of a system in the Small, Medium, or Large category. For example, if you have a high number of integrations that create a high number of system transactions, you must increase your sizing to accommodate the additional load from integrations.

The following table lists the concurrent user guidelines for a deployment size:

Deployment sizeResilient concurrent usersMaximum concurrent users
Compact
Not applicable200
Small200400
Medium400800
Large8001750


Important

Compact is the deployment size for nonproduction environments and does not support High Availability (HA).

Considerations when building a Kubernetes cluster 

There are several considerations when building a Kubernetes cluster regarding sizing before considering the application requirements. The application requirements are meant to be included in addition to your other resource requirements. This could include but not be limited to:

  • Kubernetes control plane nodes
  • Host operating system requirements of worker nodes
  • Kubernetes management software requirements
  • Additional software (for example: monitoring software) that is deployed on the cluster

It is important to refer to your distributors and vendors to make sure additional requirements are also included in any cluster planning.

Kubernetes cluster requirements

For a successful deployment and operation of BMC Helix Service Management, make sure that specific hardware resources are available to all applications.  

The following table lists the minimum amount of available compute resource requirements for the Service Management applications:

Deployment size

Required vCPU

RAM (GB)

Compact

29

124

Small

45 

190

Medium

51

254

Large

55

279

Kubernetes quotas

Set up quotas on the cluster namespaces to enforce maximum scheduled requests and limits. If you schedule additional workloads beyond the configured quotas, the Kubernetes cluster might prevent the scheduling and affect operations in the namespace.

Important

To avoid issues related to scaling and consumption of microservices, it's important to follow recommended namespace quota settings based on your deployment size.

The following table lists the recommended settings:

BMC Helix Service Management namespace quotas 

Deployment size

CPU requests

(milli core) 

CPU limits

(milli core) 

Memory requests

(GB) 

Memory limits

(GB) 

Compact 

13650 

52100 

52 

117

Small 

27800 

129200 

105 

260

Medium 

33000

148000 

168 

331

Large 

36900 

199888

194

363

BMC Helix Platform namespace quotas 

Deployment size

CPU requests

(milli core) 

CPU limits

(milli core) 

Memory requests

(GB) 

Memory limits

(GB) 

Compact 

15380

81200

72

157

Small 

17650

115200

86

182

Medium 

17650 

115200

86

182

Large 

17650

115200 

86

182

Kubernetes node requirements

Make sure that your cluster maintains a minimum number of worker nodes to provide a high availability environment for the application data lakes. 

To support the loss of worker nodes in your cluster, you must provide extra worker nodes with resources equal to your largest worker node. As a result, if one worker node goes down, you will still maintain the minimum number of resources required to recover the application.

For example, if you have four worker nodes of 10 vCPU and 50 GB RAM, you will need a 5th worker node of 10 vCPU and 50 GB RAM to recover an application without having any impact due to the loss of a worker node. 

Important

The total amount of vCPU and RAM resources selected for the worker nodes must match or exceed the required vCPU and RAM specified in the Kubernetes cluster sizing requirements.

Deployment sizeMinimum worker nodes
Compact4
Small4
Medium4
Large4

Database resource requirements

The following table lists the BMC Helix Innovation Suite database resource requirements:

Deployment Size

vCPU

RAM (GB)

Compact (100 users maximum)

10

20

Compact (200 users maximum)

20

40

Small

24

64

Medium

40

64

Large

64

80

Important

You must set up the database server outside the Kubernetes clusters on a physical or virtual machine.

Persistent volume requirements

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

The following tables lists the disk requirements:

Deployment sizeBlock storage (GB)

Compact

1400

Small

1700

Medium

1700

Large

1700

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

Specification 

Deployment size

Compact 

Small 

Medium 

Large 

Average latency 

< 100ms 

< 100ms  

< 100ms 

< 100ms  

Write throughput 

20 MB/s 

150 MB/s 

165 MB/s 

200 MB/s 

Read throughput 

100 MB/s 

800 MB/s 

1 GB/s 

1.2 GB/s 

IOPS Write 

1K 

3K 

3.2K 

3.5K 

IOPS Read 

3K 

10K 

11K 

12K 

Multi-instance deployments

BMC Helix Service Management supports multi-instance deployments. You can deploy new instances of BMC Helix Service Management in multiple namespaces that utilize the same BMC Helix Platform.
For multi-instance deployments, consider the following points:

  • Load profile requirements are the combined requirements of BMC Helix Service Management and BMC Helix Platform Common Services load profiles.
    If your requirements exceed a combined load profile, contact  BMC Support Open link to confirm the required cluster resources.
  • Disk space requirements are increased by approximately 250 GB times the number of instances connecting to the BMC Helix Platform.
    This number might vary depending on the individual instances. 

  • Cluster resource requirements are in addition to the BMC Helix Service Management namespace and BMC Helix Platform namespace quota.
  • Database requirements are the combined requirements based on the deployment size.

BMC Helix ITSM Insights resource requirements

BMC Helix ITSM Insights Open link provides native AI Service Management capabilities with the BMC Helix Platform. BMC Helix ITSM Insights uses Natural Language Processing (NLP) and AI clustering algorithms to deliver use cases such as proactive problem management and real-time incident correlation.

Installation of ITSM Insights is optional. You must add the resource requirements listed in the table below to the overall infrastructure sizing requirements of your BMC Helix Service Management deployment. Sizing for ITSM Insights is based on data volumes rather than concurrent users.

Best practice

We recommend that you use the matching category for your overall deployment.

For example, if you have a Large size BMC Helix Service Management deployment you must use the Large ITSM Insights category, even if your concurrent users are below the maximum supported.

The following table lists the additional ITSM Insights resource requirements:

CategoryConcurrent usersIncidents per day

CPU (core)

RAM (GB)

Compact

101000

111

237

Small

255000

132

315

Medium

5010000

158

409

Large

10015000

285

756

CPU requirements

The CPU speed must be 2.4 GHz or higher.

Worker and master node disk requirements

Kubernetes master and worker nodes require a free disk space allocation of 150 GB each for container images.

Disaster recovery requirement

If you enable disaster recovery, you will need an additional processor, memory, and disk space to operate successfully. The following guidance is based on using the default disaster recovery configurations. Any modification to these settings might impact the amount of disk storage that is necessary and must be recalculated.   
The following tables list the additional resources required in the Kubernetes cluster (per data center):  

Category  

CPU (Core)  

RAM (GB)  

PVC (GB)  

Compact  

 

10  

500 

Small  

 

16  

500 

Medium  

 

16  

500 

Large  

 

16  

500 

The following tables list the additional recommendations to add to the namespace quotas (per data center):  

BMC Helix Service Management Namespace Quotas (DR Additions)  

Category  

CPU requests (milli core)  

CPU limits (milli core)  

Memory requests (GB)  

Memory limits (GB)  

Compact  

5,100  

12,200  

10  

26  

Small  

8,400  

25,400  

16 

53 

Medium  

8,400  

25,400  

16 

53 

Large  

8,400  

25,400  

16 

53 

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

Comments

  1. Conrad Pereira

    Hi,

    The Read Throughput is more than the Write Throughput while the IOPS Write is less than the IOPS Read. Is this information correct?

    Please clarify. Thanks

    Nov 16, 2023 04:47
    1. Don Burgess

      The device profile enables the application to be more responsive by providing lower latency read operations and capable of handling many write operations. This is ideal for real-time applications.

      Nov 27, 2023 10:09
  2. SudeepKumar Chandrasekaran

    Why is cluster requirements changed so drastically in 22 version ? in 21.3 it was CPU (129) and in 22.1 it shows 29 as CPU for same compact size. is this an error ?

    Dec 11, 2023 04:31
    1. Poonam Morti

      Hi SudeepKumar,

      The 21.3.05 sizing guidelines included the infrastructure sizing requirement for Smart Reporting and BMC Helix Business Workflows.

      However, starting with the 21.3.06 version, we are not including Smart Reporting and BMC Helix Business Workflows in the tests and in the sizing guidelines. This has reduced the CPU requirement.

      We are striving towards optimizing sizing footprints, and the requirements specified in the guidelines are the minimum cluster requirements.

      Thanks,

      Poonam

      Dec 18, 2023 04:45