All the node specifications of PolarDB O Edition are dedicated nodes. The dedicated nodes indicate that the CPU, memory, storage, and I/O resources allocated to the nodes are dedicated to these nodes and are not shared by other nodes. Therefore, the performance of the dedicated nodes is more stable and reliable.
PolarDB O Edition provides nodes of the following specifications for your choice.
|Node type||CPU and memory||Maximum storage capacity||Maximum number of connections||Internal bandwidth||Maximum IOPS||I/O bandwidth|
|5 TB||800||1 Gbps||16,000||1 Gbps|
|10 TB||1600||10 Gbps||64,000||4 Gbps|
|10 TB||3,200||10 Gbps||128,000||8 Gbps|
|30 TB||10,000||10 Gbps||160,000||10 Gbps|
|50 TB||12,000||10 Gbps||256,000||16 Gbps|
|50 TB||20,000||10 Gbps||384,000||24 Gbps|
|100 TB||51,200||10 Gbps||409,600||24 Gbps|
|100 TB||76,800||25 Gbps||512,000||32 Gbps|
- A PolarDB cluster that has 2 CPU cores and 8 GB of memory provides the basic specifications that are required in tests, trials, and other light-load scenarios. We recommend that you do not use clusters of this type in heavy-load production environments. In production environments, we recommend that you use clusters that have at least 8 cores and 32 GB of memory.
- You can specify a type of primary node when you create a Cluster Edition cluster. The same node type is automatically applied to read-only nodes.
- The maximum input/output operations per second (IOPS) is a theoretical value.
- The maximum number of connections for a cluster varies based on the node specifications of the cluster. If you add nodes to a cluster, the number of connections to the cluster remains unchanged.
- If you require a larger storage capacity of Archive Database compute nodes, Submit a ticket to increase the maximum storage capacity to 200 TB.