Performance test results
Detailed transaction count and response time for the performance test
The excel sheet () 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 | 60 |
2 | Brokering TC2 - Create Incident Activity Note with Author | 181 | |
3 | Brokering TC3 (Sync Service Cloud Case Comment) with author | 176 | |
4 | Brokering TC4 (Sync Service Cloud ) | 176 | |
DevOps Integration with Atlassian JIRA Software For Change Request & Incident of Remedy | 1 | DevOps TC1 - Create Change | 975 |
2 | DevOps TC2 - Create Change Activity Note with Author | 1214 | |
3 | DevOps TC3 (Sync JIRA Issue Comment) with author | 1147 | |
4 | DevOps TC4 (Sync JIRA Issue ) | 1147 | |
5 | DevOps TC5 - Create DevOps Incident | 1184 | |
6 | DevOps TC6 - Create DevOps Change | 1163 | |
7 | DevOps TC7 - Create Incident | 896 | |
Brokering Integration with Vendor Remedy ITSM | 1 | Brokering TC1 - Create Brokered Incident -Vendor ITSM | 1089 |
Ticket Consolidation with Vendor Remedy ITSM | 1 | Ticket Consolidation TC1 - Create Incident from Vendor ITSM | 1162 |
2 | Ticket Consolidation TC3 - Sync Vendor ITSM Incident Worklog | 1126 | |
3 | Ticket Consolidation TC4 - Sync Vendor ITSM Incident | 1126 | |
DevOps Integration with JIRA for Problem of Remedy | 1 | DevOps TC8 - Create DevOps Problem | 1133 |
2 | DevOps TC9 - Create Problem Activity Note with Author | 1130 | |
DevOps Integration with JIRA for Work Order of Remedy | 1 | DevOps TC10 - Create DevOps WorkOrder | 1104 |
2 | DevOps TC11 - Create Work Order Activity Note with Author | 1190 | |
3 | DevOps TC12 - Create Work Order from Jira Issue | 879 | |
DevOps Integration with Microsoft Azure for Incident of Remedy | 1 | DevOps TC13 - Create DevOps Azure ( Remedy to Azure ) | 1162 |
2 | DevOps TC14 - Create Incident in Remedy From Azure DevOps | 984 | |
Total Count | 20404 | ||
System resource utilization
The following table summarizes the resource utilization during the workload execution.
System Resource - Average Percentage of CPU | 1000 Users |
BMC Helix Platform server AR1 - 4 CPU 8 GB | 52 |
BMC Helix Platform server AR2 - 4 CPU 8 GB | 41 |
BMC Helix Platform server AR3 - 4 CPU 8 GB | 36 |
BMC Helix Multi-Cloud Service Management server's Postgres Server DB - 8 CPU 32 GB | 26 |
Integration Controller server for Tenant1 - 2 CPU 8 GB | 39 |
Integration Controller server for Tenant2 - 2 CPU 8 GB | 34 |
Integration Controller server for Tenant3 - 4 CPU 8 GB | 19 |
JIRA Instance Server - 8 CPU 32 GB | 63 |
Remedy AR System server for Tenant1- 8 CPU 20 GB | 37 |
Remedy AR System server for Tenant2 - 8 CPU 20 GB | 31 |
Remedy AR System server for Tenant3 - 8 CPU 20 GB | 29 |
SmartIT Server for Tenant1 4 CPU 12 GB | 7 |
SmartIT Server for Tenant2 4 CPU 12 GB | 7 |
SmartIT Server for Tenant3 4 CPU 12 GB | 7 |
Remedy AR System server for Vendor 1- 8 CPU 20 GB | 6 |
AR System Server for Vendor 2 - 8 CPU 20 GB | 8 |
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 |
SmartIT Server for Vendor 2 4 CPU 12 GB | 1 |
SmartIT Server for Vendor 3 4 CPU 12 GB | 1 |
BMC Helix Integration Service server utilization hosted on AWS
This excel sheet () describes the BMC Helix Integration Service server's utilization. These servers were hosted on an AWS platform managed using Kubernetes deployment.
BMC Helix Integration Service server's AWS EC2 Instance's CPU Usage - Application Server and Postgres DB Server.
Database entries
The following table summarizes entries created in the BMC Helix Multi-Cloud Service Management database during the hour long performance test.
Entries in BMC Helix Multi-Cloud Service Management Database |
| 1000 Users | ||
|---|---|---|---|---|
Tenant1 | Tenant2 | Tenant3 | ||
VendorData | 4018 | 3860 | 3913 | |
Incident | 2232 | 2154 | 2151 | |
Change | 719 | 678 | 741 | |
Problem | 386 | 374 | 373 | |
Work Order | 681 | 654 | 648 | |
Worklog | 7443 | 7188 | 7429 | |
ActiveVendortickets | 2232 | 2154 | 2151 | |
BrokeredIncidents | 2232 | 2154 | 2151 | |
Flow Transaction | 0 | 0 | 0 | |
Issues Created in JIRA DB | 7338 | |||