Cluster
- For details about the service model corresponding to the service model number, see Table 3.
- Operations per Second (OPS): number of operations executed per second by a database
- In different service models, 10 million rows of data are preset for DB instances 3.4 with different shard specifications. For details about the test OPS, see the content in bold in Table 1.
Table 1 Weak consistency: Test OPS of the database with 10 million rows of data. shard Class
Service Model No.
s1
s6
s5
s4
s3
s2
2 vCPUs | 4 GB
20546
18399
14004
15564
17802
10707
2 vCPUs | 8 GB
21070
30860
16188
19132
22058
10861
4 vCPUs | 8 GB
38274
48373
16896
21819
23210
11176
4 vCPUs | 16 GB
46871
79785
32461
74824
44682
21172
8 vCPUs | 16 GB
67178
101073
33648
108414
50272
22424
8 vCPUs | 32 GB
69476
111216
59425
110668
79308
36546
16 vCPUs | 32 GB
72242
116774
62416
116201
83223
38373
16 vCPUs | 64 GB
78146
115603
65235
123473
87620
46229
32 vCPUs | 64 GB
81271
120227
67144
126411
91124
46078
32 vCPUs | 128 GB
100947
150002
77951
147812
104516
55456
64 vCPUs | 128 GB
108013
160502
83407
157158
112632
58737
64 vCPUs | 256 GB
130382
192911
93939
192024
136045
60612
- In different service models, 100 million rows of data are preset for DB instances 3.4 with different shard specifications. For details about the test OPS, see the content in bold in Table 2.
Table 2 Weak consistency: Test OPS of the database with 100 million rows of data. shard Class
Service Model No.
s1
s6
s5
s4
s3
s2
2 vCPUs | 4 GB
8709
17810
13717
15208
11540
8534
2 vCPUs | 8 GB
11384
22770
14892
20402
14809
9621
4 vCPUs | 8 GB
18510
22912
15082
20488
14820
12098
4 vCPUs | 16 GB
20982
23130
15612
20557
19209
12839
8 vCPUs | 16 GB
28906
23642
16396
20614
19599
12917
8 vCPUs | 32 GB
36881
26361
17059
21012
19647
13452
16 vCPUs | 32 GB
38735
27679
17411
22062
20423
14124
16 vCPUs | 64 GB
52220
39560
17493
29034
22123
13553
32 vCPUs | 64 GB
54308
41142
17192
30095
22507
14395
32 vCPUs | 128 GB
67345
50946
18348
37578
29329
17082
64 vCPUs | 128 GB
71059
53512
19432
40318
31782
18277
64 vCPUs | 256 GB
87877
66258
22917
47367
37631
22841
- In different service models, 10 million rows of data are preset for DB instances 4.0 with different shard specifications. For details about the test OPS, see the content in bold in Table 3.
Table 3 Weak consistency: Test OPS of the database with 10 million rows of data. shard Class
Service Model No.
s1
s6
s5
s4
s3
s2
2 vCPUs | 4 GB
19930
18031
13654
15268
17482
10471
2 vCPUs | 8 GB
20438
30243
15783
18768
21661
10622
4 vCPUs | 8 GB
37126
47406
16474
21404
22792
10930
4 vCPUs | 16 GB
45465
78189
31649
73402
43878
20706
8 vCPUs | 16 GB
65163
99052
32807
106354
49367
21931
8 vCPUs | 32 GB
67392
108992
57939
108565
77880
35742
16 vCPUs | 32 GB
70661
115441
60135
113993
81174
37629
16 vCPUs | 64 GB
75802
113291
63604
121127
86043
45212
32 vCPUs | 64 GB
78834
117822
66148
125972
89484
47020
32 vCPUs | 128 GB
97919
147002
76002
145004
102635
54236
64 vCPUs | 128 GB
105773
159292
82722
159154
113819
57532
64 vCPUs | 256 GB
126471
189053
91591
188376
133596
59279
- In different service models, 100 million rows of data are preset for DB instances 4.0 with different shard specifications. For details about the test OPS, see the content in bold in Table 4.
Table 4 Weak consistency: Test OPS of the database with 100 million rows of data. shard Class
Service Model No.
s1
s6
s5
s4
s3
s2
2 vCPUs | 4 GB
8448
17454
13374
14919
11332
8346
2 vCPUs | 8 GB
11042
22315
14520
20014
14542
9409
4 vCPUs | 8 GB
17955
22454
14705
20099
14553
11832
4 vCPUs | 16 GB
20353
22667
15222
20166
18863
12557
8 vCPUs | 16 GB
28039
23169
15986
20222
19246
12633
8 vCPUs | 32 GB
35775
25834
16633
20613
19293
13156
16 vCPUs | 32 GB
37163
26725
17464
21643
20657
13813
16 vCPUs | 64 GB
50653
38769
17056
28482
21725
13255
32 vCPUs | 64 GB
52679
40319
17738
29621
22594
13785
32 vCPUs | 128 GB
65325
49927
17889
36864
28801
16706
64 vCPUs | 128 GB
71397
52421
18941
39414
31817
18675
64 vCPUs | 256 GB
85241
64933
22344
46467
36954
22338
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.