PolarDB for MySQL provides Cluster Edition, Single Node, and Archive Database editions. Each edition provides different specifications of compute nodes. The following sections show the specifications of compute nodes in PolarDB for MySQL:
- All nodes in clusters of Cluster Edition are dedicated nodes. The computing resources such as CPUs that are allocated to each cluster are exclusive to the cluster. This improves the stability and reliability.
- Single Node uses nodes of the burstable performance type and shares resources in a computing resource pool. This improves resource usage. The Single Node architecture also saves resource costs because no proxy is required.
- By default, a Archive Database cluster uses one dedicated node. This saves the expenses on PolarProxy and reduces the overheads of synchronizing redo logs.
| Edition | Node specification code | CPU and memory | Maximum storage capacity | Maximum number of connections | Internal bandwidth | Maximum IOPS | I/O bandwidth |
|---|---|---|---|---|---|---|---|
| Cluster Edition | polar.mysql.x4.medium | 2 cores, 8 GB | 5 TB | 2,000 | 1 Gbps | 8,000 | 1 Gbps |
| polar.mysql.x4.large | 4 cores, 16 GB | 10 TB | 8,000 | 10 Gbps | 32,000 | 4 Gbps | |
| polar.mysql.x4.xlarge | 8 cores, 32 GB | 20 TB | 10,000 | 10 Gbps | 64,000 | 8 Gbps | |
| polar.mysql.x8.xlarge | 8 cores, 64 GB | 30 TB | 10,000 | 10 Gbps | 72,000 | 10 Gbps | |
| polar.mysql.x8.2xlarge | 16 cores, 128 GB | 100 TB | 20,000 | 10 Gbps | 128,000 | 16 Gbps | |
| polar.mysql.x8.4xlarge | 32 cores, 256 GB | 100 TB | 64,000 | 10 Gbps | 192,000 | 24 Gbps | |
| polar.mysql.x8.8xlarge | 64 cores, 512 GB | 100 TB | 64,000 | 10 Gbps | 192,000 | 24 Gbps | |
| polar.mysql.x8.12xlarge | 88 cores, 710 GB | 100 TB | 64,000 | 25 Gbps | 256,000 | 32 Gbps | |
| Single Node | polar.mysql.s2.large | 4 cores, 8 GB | 5 TB | 1,200 | 1 Gbps | 8,000 | 1 Gbps |
| Archive Database | polar.mysql.a4.large | 4 cores, 16 GB | 50 TB | 8,000 | 10 Gbps | 32,000 | 4 Gbps |
| polar.mysql.a4.xlarge | 8 cores, 32 GB | 100 TB | 10,000 | 10 Gbps | 64,000 | 8 Gbps | |
| polar.mysql.a8.xlarge | 8 cores, 64 GB | 100 TB | 10,000 | 10 Gbps | 72,000 | 10 Gbps | |
| polar.mysql.a8.2xlarge | 16 cores, 128 GB | 100 TB | 20,000 | 10 Gbps | 128,000 | 16 Gbps | |
| polar.mysql.a8.4xlarge | 32 cores, 256 GB | 100 TB | 64,000 | 10 Gbps | 192,000 | 24 Gbps | |
| polar.mysql.a8.8xlarge | 64 cores, 512 GB | 100 TB | 64,000 | 10 Gbps | 192,000 | 24 Gbps | |
| polar.mysql.a8.12xlarge | 88 cores, 710 GB | 100 TB | 64,000 | 25 Gbps | 256,000 | 32 Gbps |
Note
- 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 have higher requirements on the storage of Archive Database compute nodes, Submit a ticket to increase the maximum storage capacity to 200 TB.