PolarDB MySQL is available in two editions: Cluster Edition and Multi-master Cluster (Database/Table) Edition. Specifications of compute nodes vary based on the edition of the nodes. This topic describes the latest specifications of compute nodes.
Specifications of compute nodes in different editions
The following sections describe the specifications of compute nodes in different PolarDB for MySQL editions:
A cluster of Cluster Edition or Multi-master Cluster (Database/Table) Edition supports the General-purpose and Dedicated specifications.
Dedicated: Computing resources such as CPUs that are allocated to each cluster are exclusive to the cluster. This improves the stability and reliability.
General-purpose: Idle computing resources such as CPUs are shared among clusters on the same server for cost-effectiveness.
Cluster Edition
Edition | Node instance type | CPU and memory | Maximum storage capacity | Maximum connections | Maximum inodes in a file system1 | Maximum blktags in a file system2 | PSL4 maximum IOPS | PSL5 maximum IOPS | I/O bandwidth |
Cluster Edition (Dedicated) | polar.mysql.x4.medium | 2 cores, 8 GB memory | 5 TB | 6,000 | 1,048,576 | 1,310,720 | 8,000 | 16,000 | 1 Gbps |
polar.mysql.x8.medium | 2 cores, 16 GB memory | 10 TB | 8000 | 2,097,152 | 2,621,440 | 18,000 | 36,000 | 2 Gbps | |
polar.mysql.x4.large | 4 cores, 16 GB memory | 10 TB | 8,000 | 2,097,152 | 2,621,440 | 32,000 | 64,000 | 4 Gbps | |
polar.mysql.x8.large | 4 cores, 32 GB memory | 10 TB | 8000 | 2,097,152 | 2,621,440 | 36,000 | 72,000 | 4 Gbps | |
polar.mysql.x4.xlarge | 8 cores, 32 GB memory | 20 TB | 10,000 | 4,194,304 | 5,242,880 | 48,000 | 96,000 | 8 Gbps | |
polar.mysql.x8.xlarge | 8 cores, 64 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 54,000 | 108,000 | 10 Gbps | |
polar.mysql.x4.2xlarge | 16 cores, 64 GB memory | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 96,000 | 192,000 | 16 Gbps | |
polar.mysql.x8.2xlarge | 16 cores, 128 GB memory | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 96,000 | 192,000 | 16 Gbps | |
polar.mysql.x4.4xlarge | 32 cores, 128 GB memory | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 144,000 | 288,000 | 20 Gbps | |
polar.mysql.x8.4xlarge | 32 cores, 256 GB memory | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 144,000 | 288,000 | 24 Gbps | |
polar.mysql.x8.8xlarge | 64 cores, 512 GB memory | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 144,000 | 288,000 | 24 Gbps | |
polar.mysql.x8.12xlarge | 88 cores, 710 GB memory | 100 TB | 100,000 | 20,971,520 | 26,214,400 | 192,000 | 384,000 | 32 Gbps | |
polar.mysql.x8.15xlarge | 120 cores, 920 GB memory | 100 TB | 130,000 | 20,971,520 | 26,214,400 | 261,500 | 523,000 | - | |
Cluster Edition (General-purpose) | polar.mysql.g2.medium | 2 cores, 4 GB memory | 5 TB | 1,800 | 1,048,576 | 1,310,720 | 4,000 | 8,000 | 1 Gbps |
polar.mysql.g4.medium | 2 cores, 8 GB memory | 5 TB | 2,000 | 1,048,576 | 1,310,720 | 8,000 | 16,000 | 1 Gbps | |
polar.mysql.g2.large | 4 cores, 8 GB memory | 10 TB | 3,000 | 2,097,152 | 2,621,440 | 15,000 | 30,000 | 2 Gbps | |
polar.mysql.g4.large | 4 cores, 16 GB memory | 10 TB | 6,000 | 2,097,152 | 2,621,440 | 21,000 | 42,000 | 2 Gbps | |
polar.mysql.g2.xlarge | 8 cores, 16 GB memory | 10 TB | 6,000 | 2,097,152 | 2,621,440 | 18,000 | 36,000 | 2 Gbps | |
polar.mysql.g4.xlarge | 8 cores, 32 GB memory | 20 TB | 10,000 | 4,194,304 | 5,242,880 | 27,000 | 54,000 | 4 Gbps | |
polar.mysql.g4.2xlarge | 16 cores, 64 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 4 Gbps | |
polar.mysql.g6.2xlarge | 16 cores, 96 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps | |
polar.mysql.g8.2xlarge | 16 cores, 128 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps | |
polar.mysql.g4.4xlarge | 32 cores, 128 GB memory | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 42,000 | 84,000 | 8 Gbps |
Multi-master Cluster (Database/Table) Edition
Edition | Node instance type | CPU and memory | Maximum storage capacity | Maximum connections | Maximum inodes in a file system1 | Maximum blktags in a file system2 | PSL4 maximum IOPS | PSL5 maximum IOPS | I/O bandwidth |
Multi-master Cluster (Database/Table) Edition (Dedicated) | polar.mysql.mmx4.xlarge | 8 cores, 32 GB memory | 20 TB | 10,000 | 4,194,304 | 5,242,880 | 48,000 | 96,000 | 8 Gbps |
polar.mysql.mmx8.xlarge | 8 cores, 64 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 54,000 | 108,000 | 10 Gbps | |
polar.mysql.mmx4.2xlarge | 16 cores, 64 GB memory | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 96,000 | 192,000 | 16 Gbps | |
polar.mysql.mmx8.2xlarge | 16 cores, 128 GB memory | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 96,000 | 192,000 | 16 Gbps | |
polar.mysql.mmx4.4xlarge | 32 cores, 128 GB memory | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 144,000 | 288,000 | 20 Gbps | |
polar.mysql.mmx8.4xlarge | 32 cores, 256 GB memory | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 144,000 | 288,000 | 24 Gbps | |
polar.mysql.mmx8.8xlarge | 64 cores, 512 GB memory | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 144,000 | 288,000 | 24 Gbps | |
polar.mysql.mmx8.12xlarge | 88 cores, 710 GB memory | 100 TB | 100,000 | 20,971,520 | 26,214,400 | 192,000 | 384,000 | 32 Gbps | |
Multi-master Cluster (Database/Table) Edition (General-purpose) | polar.mysql.mmg2.xlarge | 8 cores, 16 GB memory | 10 TB | 6,000 | 2,097,152 | 2,621,440 | 18,000 | 63,000 | 2 Gbps |
polar.mysql.mmg4.xlarge | 8 cores, 32 GB memory | 20 TB | 10,000 | 4,194,304 | 5,242,880 | 27,000 | 54,000 | 4 Gbps | |
polar.mysql.mmg4.2xlarge | 16 cores, 64 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 4 Gbps | |
polar.mysql.mmg6.2xlarge | 16 cores, 96 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps | |
polar.mysql.mmg8.2xlarge | 16 cores, 128 GB memory | 30 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps | |
polar.mysql.mmg4.4xlarge | 32 cores, 128 GB memory | 60 TB | 32,000 | 12,582,912 | 15,728,640 | 63,000 | 126,000 | 8 Gbps |
Maximum inodes in a file system1 and maximum blktags in a file system2
PolarDB uses the self-developed distributed file system Polar File System (PolarFS) to access underlying storage. Similar to traditional file systems, PolarFS contains inodes and blktags. An inode corresponds to a file. A blktag corresponds to 4 MB of logical space on Elastic Block Storage (EBS). The numbers of inodes and blktags are linearly related to the storage capacity. For example, a 10-GB disk has a maximum of 2,048 inodes and 2,560 blktags. If the maximum capacity, maximum number of inodes, or maximum number of blktags is reached, you must upgrade the specifications.
Conversion of capacity units:
1 TB=1,024 GB
1 GB=1,024 MB
1 MB=1,024 KB
1 KB=1,024 Byte
The maximum IOPS represents the theoretical limit. It is not guaranteed that these nominal values can be achieved under all conditions.
A PolarDB cluster that has 2 cores and 8 GB of memory is sufficient to provide the basic specifications required in tests, trials, and other light-load scenarios. We recommend that you do not use clusters of these specifications 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.
Clusters in a global database network (GDN) do not support specifications of 2 cores and 4 GB of memory or 2 cores and 8 GB of memory.
You can select specifications for the primary node when you create a cluster of Cluster Edition. The same specifications are automatically applied to read-only nodes.
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.