This topic describes the results of a performance test on an ApsaraDB RDS instance that runs SQL Server 2008 R2 on RDS High-availability Edition.
The test is based on the TPC-C benchmarks. However, the test is not an official TPC-C benchmark test. Therefore, the test results that are provided in this topic cannot be compared with the results of TPC-C benchmark tests.
For more information about ApsaraDB RDS for SQL Server, see Troubleshoot the issues of high CPU utilization on an ApsaraDB RDS for SQL Server instance.
Tested instance types
Instance type | CPU cores | Memory (GB) | IOPS |
rds.mssql.s1.small | 1 | 2 | 1000 |
rds.mssql.s2.large | 2 | 4 | 2000 |
rds.mssql.s2.xlarge | 2 | 8 | 4000 |
rds.mssql.s3.large | 4 | 8 | 5000 |
rds.mssql.m1.medium | 4 | 16 | 7000 |
rds.mssql.c1.large | 8 | 16 | 8000 |
rds.mssql.c1.xlarge | 8 | 32 | 12000 |
rds.mssql.c2.xlarge | 16 | 64 | 14000 |
rds.mssql.c2.xlp2 | 16 | 96 | 16000 |
rds.mssql.c2.2xlarge | 16 | 128 | 16000 |
Test results
No. | Instance type | TPM | Batch Request | TPS |
1 | rds.mssql.s1.small | 162000 | 2680 | 3100 |
2 | rds.mssql.s2.large | 273000 | 4370 | 4980 |
3 | rds.mssql.s2.xlarge | 293000 | 4600 | 5400 |
4 | rds.mssql.s3.large | 483000 | 7450 | 8970 |
5 | rds.mssql.m1.medium | 517800 | 8260 | 9640 |
6 | rds.mssql.c1.large | 630000 | 9950 | 11400 |
7 | rds.mssql.c1.xlarge | 647000 | 10300 | 11600 |
8 | rds.mssql.c2.xlarge | 769000 | 11700 | 13900 |
9 | rds.mssql.c2.xlp2 | 810000 | 13300 | 14200 |
10 | rds.mssql.c2.2xlarge | 840000 | 13100 | 14800 |