Phased rolloutThis documentation supports the 21.02 version of BMC Helix Multi-Cloud Broker.To view an earlier version, select the version from the Product version menu.


Performance test results

Detailed transaction count and response time for the performance test

The excel sheet ( SilkPerformerResponseTime_2008.xlsx)  provides the response time for the performance test. The integration timer includes the waiting time for verification between the source and destination systems. The integration connector configurations throttling control time was 3 minutes, that is, 3 minutes the integration flow is triggered and executed. According to the matching condition, records are processed by flow. 

Business transactions completed

The following table summarizes all business transactions created or modified in the system.

Business Transactions Completed in 1 hour

Integration

Sr No

Flow Name

1000 Users

Brokering Integration with Salesforce

1

Brokering TC1 - Create Brokered Incident 

61

2

Brokering TC2 - Create Incident Activity Note with Author

181

3

Brokering TC3 (Sync Service Cloud Case Comment) with author

117

4

Brokering TC4 (Sync Service Cloud  ) 

117

DevOps Integration with Atlassian JIRA Software

For Change Request & Incident of Remedy

1

DevOps TC1 - Create Change

979

2

DevOps TC2 - Create Change Activity Note with Author

1353

3

DevOps TC3 (Sync JIRA Issue Comment) with author

1253

4

DevOps TC4 (Sync JIRA Issue )

1253

5

DevOps TC5 - Create DevOps Incident

1376

6

DevOps TC6 - Create DevOps Change

1284

7

DevOps TC7 - Create Incident 

885

Brokering Integration with Vendor ITSM 

1

Brokering TC1 - Create Brokered Incident -Vendor ITSM

1245

Ticket Consolidation with  Vendor  ITSM

1

Ticket Consolidation TC1 - Create Incident from Vendor ITSM 

1315

2

Ticket Consolidation TC3 - Sync Vendor ITSM Incident Worklog

1241

3

Ticket Consolidation TC4 - Sync Vendor ITSM Incident

1241

DevOps Integration with JIRA

for Problem of Remedy

1

DevOps TC8 - Create DevOps Problem 

1303

2

DevOps TC9 - Create Problem Activity Note with Author

1301

DevOps Integration with JIRA for

Work Order of Remedy

1

DevOps TC10 - Create DevOps WorkOrder

1284

2

DevOps TC11 - Create Work Order Activity Note  with Author

1361

3

DevOps TC12 - Create Work Order from Jira Issue 

942

Total Count

20092

System resource utilization

The following table summarizes the resource utilization during the workload execution. 

Resource_Utilization_2008.png


System Resource - Average Percentage of CPU

1000 Users

BMC Helix Innovation Suite server AR1 - 4 CPU  8 GB

47

BMC Helix Innovation Suite server AR2 - 4 CPU  8 GB

36

BMC Helix Innovation Suite server AR3 - 4 CPU  8 GB

44

BMC Helix Multi-Cloud Broker server's Postgres Server DB - 8 CPU 32 GB

30

Integration Controller server for Tenant1 -  4 CPU 8 GB

4

Integration Controller server for Tenant2 - 4 CPU 8 GB

6

Integration Controller server for Tenant3 -  4 CPU 8 GB

3

JIRA Instance Server - 8 CPU 32 GB

49

Remedy AR System server for Tenant1- 8 CPU 20 GB

23

Remedy AR System server for Tenant2 - 8 CPU 20 GB

22

Remedy AR System server for Tenant3 -  8 CPU 20 GB

23

SmartIT Server for Tenant1  4 CPU 12 GB

5

SmartIT Server for Tenant2 4 CPU 12 GB

4

SmartIT Server for Tenant3 4 CPU 12 GB

4

Remedy AR System server for Vendor 1- 8 CPU 20 GB

8

Remedy AR System Server for Vendor 2 - 8 CPU 20 GB

8

Remedy AR System Server for Vendor 3 -  8 CPU 20 GB

7

Remedy with SmartIT (Smart IT) Server for Vendor 1  4 CPU 12 GB

1

Remedy with SmartIT (Smart IT) Server for Vendor 2 4 CPU 12 GB

1

Remedy with SmartIT (Smart IT) Server for Vendor 3 4 CPU 12 GB

1

BMC Helix Integration Service

 Postgres Server DB  4 CPU , 8 GB 


9

BMC Helix Integration Service server utilization hosted on OpenShift Cluster

This excel sheet  ( Ints_ResourceUtilizationIntegration_2008WP.xlsx) describes the BMC Helix Integration Service pod's utilization. These were hosted on an Red Hat OpenShift Container Platform managed using Kubernetes deployment. 

BMC Helix Integration Service PANAMA API pod's resource Usage . 

Tenant 1 : Jira and Remedy connectors were used from Integration Controller Site. Service Cloud and Multi-Cloud Connector was on server site. 

Tenant 2 : Jira and Remedy connectors were used from Integration Controller Site. Service Cloud and Multi-Cloud Connector was on server site. 

Tenant 3 : Jira was used from Integration Controller Site. Remedy Connector , Service Cloud and Multi-Cloud Connector was on server site. 


Pod Name

Panama API1

Panama API2

ActiveMQ-0

ActiveMQ-1

Flow Engine 1

Flow Engine 2

Multi Cloud

Connector 1

Multi Cloud

Connector 2

Remedy Connector1
  ( tenant3)

Remedy Connector2
( tenant3)

CPU usage

( in processors )

0.70

0.67

0.15

0.24

0.08

0.07

0.03

0.03

0.02

0.01


Panama_API_POD_1.pngPanama_API_POD_2.png


Database entries

The following table summarizes entries created in the BMC Helix Multi-Cloud Broker database during the hour long performance test.

Entries in

BMC Helix Multi-Cloud Broker Database

 

1000 Users

Tenant1

Tenant2

Tenant3

VendorData

3564

3565

3546

Incident

1614

1639

1629

Change

770

753

740

Problem

431

440

432

Work Order

750

733

746

Worklog

7301

7515

7359

ActiveVendortickets

1614

1639

1629

BrokeredIncidents

1614

1639

1629

Flow Transaction

4

2

4

Issues Created in JIRA DB

8078

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*