Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
Building a Hybrid Database-as-a-Service Platform with Azure Stack HCI
Overview Solution Architecture Lab Setup Performance-Oriented Test Scenarios
Test methodology introduction
HammerDB initial configuration
HammerDB CLI Configuration
SQL MI creation and configuration
Test groups defined
Test Group 1 results
Test Group 2 results
Test Group 3 Results
Test Group 4 results
Test Group 5 results
Test Group 6 results
Reporting visualizations
Testing synopsis
Functional Test Scenarios Conclusion Appendix A: On-premises monitoring setup Appendix B: SQL MI and HammerDB Test Harness details Additional Resources

Test Group 4 results

Test Group 4 results

  • In Test-4, as shown in the following figure, we increased the total number of SQL MIs running HammerDB TPC-C workloads to eight. These SQL MIs were the combined instances from Test-2 and Test-3.

    We observed a flattening out of the TPM numbers across the different instances despite having separate resource configurations running. One of the best TPM numbers was observed from the four CPU requested instance, sqlmi-04, with 20 virtual users. 

    The first four SQL MIs had four vCPUs requested, and the second four SQL MIs had 6 vCPUs requested. With the combined workload profile, we saw greater efficiency and potential Azure consumption cost savings by potentially aligning with a four vCPU configuration for this workload pattern. With SQL Server, it is always best to maximize work aligned with an efficient core count. 

    For SQL MI specifications, see Test groups defined.

    Figure 24.    Test-4 user count and TPM metrics