Replica Set
Instances of the same type have different memory specifications. You can select instances of different specifications based on application scenarios.
This section describes replica set instance specifications. The instance specifications depend on the selected CPU model.
The default maximum number of connections has been adjusted. Query the number of connections based on the instance creation time. For details about the number of connections for instances created before July 2021, see Historical Instance Specifications.
Instance Specifications
DDS replica set instances have two specification types: general-purpose and enhanced II. For details, see Table 1.
Specification Type |
Description |
Applicable Scenario |
---|---|---|
General-purpose |
CPU resources are shared with other general-purpose DB instances on the same physical machine. CPU usage is maximized through resource overcommitment. This instance class is a cost-effective option and suitable for scenarios where performance stability is not critical. |
Suitable for scenarios that have high requirements on cost-effectiveness. |
Enhanced II |
With a leading network acceleration engine and Data Plane Development Kit (DPDK) fast packet processing mechanism, this instance class provides higher network performance and computing power. |
Suitable for websites and web applications that require high database computing and network performance. |
Table 2 lists the specifications of replica set instances.
CPU Type |
Specifications |
vCPUs |
Memory (GB) |
Flavor ID |
Default Maximum Number of Connections |
Range of Connections |
---|---|---|---|---|---|---|
x86 |
General-purpose |
2 |
4 |
dds.mongodb.s6.large.2.repset |
1000 |
200-1000 |
2 |
8 |
dds.mongodb.s6.large.4.repset |
1000 |
200-1000 |
||
4 |
8 |
dds.mongodb.s6.xlarge.2.repset |
3000 |
200-3000 |
||
4 |
16 |
dds.mongodb.s6.xlarge.4.repset |
3000 |
200-3000 |
||
8 |
16 |
dds.mongodb.s6.2xlarge.2.repset |
8000 |
200-8000 |
||
8 |
32 |
dds.mongodb.s6.2xlarge.4.repset |
8000 |
200-8000 |
||
Enhanced II |
1 |
8 |
dds.mongodb.c6.medium.8.repset |
500 |
200-500 |
|
2 |
8 |
dds.mongodb.c6.large.4.repset |
1000 |
200-1000 |
||
2 |
16 |
dds.mongodb.c6.large.8.repset |
1000 |
200-1000 |
||
4 |
16 |
dds.mongodb.c6.xlarge.4.repset |
3000 |
200-3000 |
||
4 |
32 |
dds.mongodb.c6.xlarge.8.repset |
3000 |
200-3000 |
||
8 |
32 |
dds.mongodb.c6.2xlarge.4.repset |
8000 |
200-8000 |
||
8 |
64 |
dds.mongodb.c6.2xlarge.8.repset |
8000 |
200-8000 |
||
16 |
64 |
dds.mongodb.c6.4xlarge.4.repset |
16000 |
200-16000 |
||
16 |
128 |
dds.mongodb.c6.4xlarge.8.repset |
16000 |
200-16000 |
||
32 |
128 |
dds.mongodb.c6.8xlarge.4.repset |
16000 |
200-16000 |
||
32 |
256 |
dds.mongodb.c6.8xlarge.8.repset |
16000 |
200-16000 |
||
64 |
256 |
dds.mongodb.c6.16xlarge.4.repset |
16000 |
200-16000 |
||
64 |
512 |
dds.mongodb.c6.16xlarge.8.repset |
16000 |
200-16000 |
||
Kunpeng |
- |
2 |
4 |
dds.mongodb.large.arm2.repset |
1000 |
200-1000 |
- |
2 |
8 |
dds.mongodb.large.arm4.repset |
1000 |
200-1000 |
|
- |
4 |
8 |
dds.mongodb.xlarge.arm2.repset |
3000 |
200-3000 |
|
- |
4 |
16 |
dds.mongodb.xlarge.arm4.repset |
3000 |
200-3000 |
|
- |
8 |
16 |
dds.mongodb.2xlarge.arm2.repset |
8000 |
200-8000 |
|
- |
8 |
32 |
dds.mongodb.2xlarge.arm4.repset |
8000 |
200-8000 |
|
- |
16 |
32 |
dds.mongodb.4xlarge.arm2.repset |
16000 |
200-16000 |
|
- |
16 |
64 |
dds.mongodb.4xlarge.arm4.repset |
16000 |
200-16000 |
Historical Instance Specifications
For details about the range of connections of instances created before July 2021, see the following table.
CPU Type |
Specifications |
vCPUs |
Memory (GB) |
Flavor ID |
Default Maximum Number of Connections |
Range of Connections |
---|---|---|---|---|---|---|
x86 |
General-purpose |
2 |
4 |
dds.mongodb.s6.large.2.repset |
400 |
200-1000 |
2 |
8 |
dds.mongodb.s6.large.4.repset |
400 |
200-1000 |
||
4 |
8 |
dds.mongodb.s6.xlarge.2.repset |
1000 |
200-3000 |
||
4 |
16 |
dds.mongodb.s6.xlarge.4.repset |
1000 |
200-3000 |
||
8 |
16 |
dds.mongodb.s6.2xlarge.2.repset |
4000 |
200-8000 |
||
8 |
32 |
dds.mongodb.s6.2xlarge.4.repset |
4000 |
200-8000 |
||
Enhanced |
2 |
8 |
dds.mongodb.c3.large.4.repset |
400 |
200-1000 |
|
4 |
16 |
dds.mongodb.c3.xlarge.4.repset |
1000 |
200-3000 |
||
8 |
32 |
dds.mongodb.c3.2xlarge.4.repset |
4000 |
200-8000 |
||
16 |
64 |
dds.mongodb.c3.4xlarge.4.repset |
8000 |
200-16000 |
||
32 |
128 |
dds.mongodb.c3.8xlarge.4.repset |
8000 |
200-16000 |
||
60 |
256 |
dds.mongodb.c3.15xlarge.4.repset |
8000 |
200-16000 |
||
Enhanced II |
2 |
8 |
dds.mongodb.c6.large.4.repset |
400 |
200-1000 |
|
4 |
16 |
dds.mongodb.c6.xlarge.4.repset |
1000 |
200-3000 |
||
8 |
32 |
dds.mongodb.c6.2xlarge.4.repset |
4000 |
200-8000 |
||
16 |
64 |
dds.mongodb.c6.4xlarge.4.repset |
8000 |
200-16000 |
||
32 |
128 |
dds.mongodb.c6.8xlarge.4.repset |
8000 |
200-16000 |
||
64 |
256 |
dds.mongodb.c6.16xlarge.4.repset |
8000 |
200-16000 |
||
Kunpeng |
- |
2 |
4 |
dds.mongodb.large.arm2.repset |
400 |
200-1000 |
- |
2 |
8 |
dds.mongodb.large.arm4.repset |
400 |
200-1000 |
|
- |
4 |
8 |
dds.mongodb.xlarge.arm2.repset |
1000 |
200-3000 |
|
- |
4 |
16 |
dds.mongodb.xlarge.arm4.repset |
1000 |
200-3000 |
|
- |
8 |
16 |
dds.mongodb.2xlarge.arm2.repset |
4000 |
200-8000 |
|
- |
8 |
32 |
dds.mongodb.2xlarge.arm4.repset |
4000 |
200-8000 |
|
- |
16 |
32 |
dds.mongodb.4xlarge.arm2.repset |
8000 |
200-16000 |
|
- |
16 |
64 |
dds.mongodb.4xlarge.arm4.repset |
8000 |
200-16000 |
Helpful Links
- How do I change the maximum number of connections of a replica set instance?
You can change the maximum number of connections to an instance by modifying the net.maxIncomingConnections parameter. For details about how to change parameter values, see Editing a Parameter Template.
- How do I buy a replica set instance?
For details, see Buying a Replica Set Instance.
- How do I change the CPU and memory of a replica set instance?
For details, see Changing the CPU or Memory of a Replica Set Instance.
- How do I scale up the storage space of a replica set instance?
For details, see Scaling Up Storage.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot