Test cases defined
Eleven SQL MI instance test cases were defined to simulate different test scenarios and combinations. TPM results were documented for each test run. These test cases are listed in the table below.
This grouping configuration represents a good mix of Dev, Test, QA, and Production, all within the same cluster.
Table 7. Test group matrix
SQLMI-01 | General | 2vCPU, 4Gi | Test-1, Test-2 |
SQLMI-02 | General | 2vCPU, 4Gi | Test-2 |
SQLMI-03 | General | 4vCPU, 4Gi | Test-3, Test-4 |
SQLMI-04 | General | 4vCPU, 4Gi | Test-4 |
SQLMI-05 | General | 6vCPU, 8Gi | Test-5, Test-6 |
SQLMI-06 | General | 6vCPU, 8Gi | Test 6 |
SQLMI-07 | General | 8vCPU, 8Gi | Test-7, Test 8, Test-LargeMI |
SQLMI-08 | General | 8vCPU, 8Gi | Test-8, , Test-LargeMI |
SQLMI-09 | General | 16vCPU, 16Gi | Test-9, Test-10, Test-LargeMI |
SQLMI-10 | General | 16vCPU, 16Gi | Test-10, Test-LargeMI |
BIZCRTCL-01 | Business Critical | (8vCPU, 8Gi) x 3 | Test 11, Test-12, Test-13, Test-LargeMI |
BIZCRTCL-02 | Business Critical | (16vCPU, 16Gi) x 3 | Test-12, Test-13, Test-LargeMI |
BIZCRTCL-03 | Business Critical | (8vCPU, 8Gi) x 3 | Test 11, Test-12, Test-13, Test-LargeMI |
| 168 Total vCPU requested | 176GI memory requested |
Test case user count
To avoid CPU exhaustion in the HammerDB client host, the total HammerDB user counts were configured appropriately. HammerDB user count for each loop that is used during each test cases are:
- foreach z { 40 80 120 160 200 }
Note: To understand the foreach loop of the HammerDB. tcl code, see the autopilot section of the document.
