Performance workload details
The following table provides the distribution of workload across various use cases.
- Target workload for a load test of 1 hour.
- Increasing workload model was scheduled in SilkPerformer for these numbers.
For more information about the use cases, see User-scenarios-and-associated-actions.
Performance Testing Workload Breakdown - Silk Performer Scripts - 3 Tenants | |
Script | 1000 Users |
Brokering TC1 - Create Brokered Incident with Salesforce | 3 |
Brokering TC2 - Create Incident Activity Note with Author | 9 |
Brokering TC3 TC4 - Sync Salesforce Edit Comment | 9 |
DevOps TC1 - Create Change | 64 |
DevOps TC2 - Create Change Activity Note with Author | 63 |
DevOps TC3 TC4 - Sync Jira_Edit_Comment | 63 |
DevOps TC5 Create DevOps Incident | 63 |
DevOps TC6 - Create DevOps Change | 63 |
DevOps TC7 - Create Incident | 63 |
DevOps TC8 - Create DevOps Problem | 60 |
DevOps TC9 - Create Problem Activity Note with Author | 60 |
DevOps TC10 - Create DevOps Work Order | 60 |
DevOps TC11- Create Work Order Activity Note with Author | 60 |
DevOps TC12 - Create Work Order From JIRA Issue | 60 |
DevOps TC13 - Create DevOps Azure - Remedy ITSM to Azure | 60 |
DevOps TC14 -Create Incident From Azure To Remedy ITSM | 60 |
Brokering TC5 - Create Brokered Incident Vendor ITSM | 60 |
Ticket Consolidation TC1_Create Incident From Vendor ITSM | 60 |
Ticket Consolidation TC3 TC4 Sync Vendor ITSM Edit Comment | 60 |
TOTAL Number Of Users | 1000 |
Total Number of Users on each Tenant | 333 |