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's configurations throttling control time was 3 minutes, that is, 3 minutes the integration flow is triggered and executed. According to 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 | 150 Users | 300 Users | 450 Users |
Brokering Integration | 1 | Brokering TC1 - Create Brokered Incident | 114 | 179 | 344 |
2 | Brokering TC2 - Create Incident Activity Note | 183 | 361 | 507 | |
3 | Brokering TC3 - Sync Service Cloud Case Comment | 167 | 355 | 502 | |
4 | Brokering TC4 - Sync Service Cloud | 167 | 355 | 502 | |
Dev-Ops Integration | 1 | DevOps TC1 - Create Change | 341 | 742 | 813 |
2 | DevOps TC2 - Create Change Activity Note | 422 | 778 | 1196 | |
3 | DevOps TC3 - Sync JIRA Issue Comment | 387 | 727 | 1062 | |
4 | DevOps TC4 - Sync JIRA Issue | 387 | 727 | 1062 | |
5 | DevOps TC5 - Create DevOps Incident | 416 | 750 | 1195 | |
6 | DevOps TC6 - Create DevOps Change | 391 | 806 | 1147 | |
7 | DevOps TC7 - Create Incident | 316 | 668 | 871 | |
Total Count | 3291 | 6448 | 9201 | ||
System resource utilization
The following table summarizes the resource utilization during the workload execution.
System Resource - Average Percentage of CPU | 150 Users | 300 Users | 450 Users |
Multi-Cloud Innovation Server AR1 - 4 CPU 8 GB | 25 | 35 | 49 |
Multi-Cloud Innovation Server AR2 - 4 CPU 8 GB | 20 | 34 | 45 |
Multi-Cloud Server's Postgres Server DB - 8 CPU 32 GB | 11 | 20 | 31 |
Integration Controller Server for Tenant1 - 2 CPU 8 GB | 5 | 9 | 11 |
Integration Controller Server for Tenant2 - 2 CPU 8 GB | 5 | 8 | 11 |
Integration Controller Server for Tenant3 - 4 CPU 8 GB | 3 | 4 | 6 |
JIRA Instance Server - 8 CPU 32 GB | 9 | 18 | 23 |
AR System Server for Tenant1- 8 CPU 20 GB | 5 | 10 | 12 |
AR System Server for Tenant2 - 8 CPU 20 GB | 5 | 8 | 12 |
AR System Server for Tenant3 - 8 CPU 20 GB | 8 | 13 | 15 |
SmartIT Server for Tenant1 4 CPU 12 GB | 2 | 3 | 4 |
SmartIT Server for Tenant2 4 CPU 12 GB | 1 | 2 | 3 |
SmartIT Server for Tenant3 4 CPU 12 GB | 2 | 3 | 3 |
ITSM DB 40 CPU 512 GB ( Shared Instance) | 5 | 9 | 3 |
Integration Server Utilization hosted on AWS
This excel sheet () describes the Integration Server's utilization. These servers were hosted on AWS platform managed using Kubernetes deployment.
The following table summarizes entries created in the BMC Helix Multi-Cloud Service Management database during the hour long performance test.
Entries in Multi-Cloud DB | 150 Users | 300 Users | 450 Users | ||||||||
Tenant1 | Tenant2 | Tenant3 | Tenant1 | Tenant2 | Tenant3 | Tenant1 | Tenant2 | Tenant3 | |||
VendorData | 526 | 489 | 564 | 1087 | 969 | 1097 | 1487 | 1440 | 1464 | ||
Incident | 281 | 276 | 289 | 562 | 479 | 564 | 791 | 849 | 772 | ||
Change | 245 | 213 | 275 | 526 | 490 | 533 | 697 | 591 | 692 | ||
Worklog | 1118 | 1052 | 1167 | 2259 | 1999 | 2253 | 3206 | 3025 | 3128 | ||
ActiveVendortickets | 142 | 141 | 147 | 290 | 267 | 298 | 390 | 452 | 375 | ||
BrokeredIncidents | 281 | 276 | 289 | 562 | 479 | 564 | 791 | 849 | 772 | ||
Flow Transaction | 0 | 0 | 1 | 3 | 3 | 0 | 2 | 1 | 3 | ||
Issues Created in JIRA DB | 1465 | 2973 | 4047 | ||||||||