Performance workload details
The following table provides the workload distribution across various use cases.
- Target workload during an hour of load testing.
- Increasing workload model was used to schedule in SilkPerformer for these numbers.
- For more information on use case details, follow the link, User-scenarios-and-associated-actions.
Performance Testing Workload Breakdown - Silk Performer Scripts - 3 Tenants | |||
Script | 150 Users | 300 Users | 450 Users |
Brokering TC1 - Create Brokered Incident | 6 | 9 | 18 |
BrokeringTC2_CreateIncidentActivityNote | 9 | 18 | 27 |
BrokeringTC3TC4_Sync_Salesforce_Edit_Comment | 9 | 18 | 27 |
DevOpts_TC1_CreateChange | 21 | 45 | 63 |
DevOpts_TC2_CreateChangeActivityNote | 21 | 42 | 63 |
DevOpts_TC3TC4_SyncJira_Edit_Comment | 21 | 42 | 63 |
DevOpts_TC5_CreateDevOptsIncident | 21 | 42 | 63 |
DevOps TC6 - Create DevOps Change | 21 | 42 | 63 |
DevOps TC7 - Create Incident | 21 | 42 | 63 |
TOTAL Number Of Users | 150 | 300 | 450 |
Total Number of Users on each Tenant | 50 | 100 | 150 |
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*