General-purpose and dedicated specifications
A PolarDB cluster of Cluster Edition or Multi-master Cluster (Database/Table) Edition supports the General-purpose and Dedicated specifications.
Dedicated: Each cluster does not share allocated compute resources such as CPUs with other clusters on the same server, which improves the reliability and stability of the cluster.
General-purpose: Idle compute resources such as CPUs are shared among clusters on the same server, which is more cost-effective.
Compute node specifications
Cluster Edition
Dedicated
Node type | CPU and memory | Maximum storage capacity | Maximum number of connections1 (default) | Maximum number of inodes in the file system2 | Maximum number of blktags in the file system3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.x4.medium | 2 cores, 8 GB memory | 100 TB | 6,000 | 1,048,576 | 1,310,720 | 8,000 | 16,000 | 1 Gbps |
polar.mysql.x8.medium | 2 cores, 16 GB memory | 100 TB | 8000 | 2,097,152 | 2,621,440 | 18,000 | 36,000 | 2 Gbps |
polar.mysql.x4.large | 4 cores, 16 GB memory | 100 TB | 8,000 | 2,097,152 | 2,621,440 | 32,000 | 64,000 | 4 Gbps |
polar.mysql.x8.large | 4 cores, 32 GB memory | 100 TB | 8000 | 2,097,152 | 2,621,440 | 36,000 | 72,000 | 4 Gbps |
polar.mysql.x4.xlarge | 8 cores, 32 GB memory | 100 TB | 10,000 | 4,194,304 | 5,242,880 | 48,000 | 96,000 | 8 Gbps |
polar.mysql.x8.xlarge | 8 cores, 64 GB memory | 100 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 | 100,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 | 150,000 | 20,971,520 | 26,214,400 | 261,500 | 523,000 | - |
General-purpose
Node type | CPU and memory | Maximum storage capacity | Maximum number of connections1 (default) | Maximum number of inodes in the file system2 | Maximum number of blktags in the file system3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.g2.medium | 2 cores, 4 GB memory | 100 TB | 1,800 | 1,048,576 | 1,310,720 | 4,000 | 8,000 | 1 Gbps |
polar.mysql.g4.medium | 2 cores, 8 GB memory | 100 TB | 2,000 | 1,048,576 | 1,310,720 | 8,000 | 16,000 | 1 Gbps |
polar.mysql.g2.large | 4 cores, 8 GB memory | 100 TB | 3,000 | 2,097,152 | 2,621,440 | 15,000 | 30,000 | 2 Gbps |
polar.mysql.g4.large | 4 cores, 16 GB memory | 100 TB | 6,000 | 2,097,152 | 2,621,440 | 21,000 | 42,000 | 2 Gbps |
polar.mysql.g2.xlarge | 8 cores, 16 GB memory | 100 TB | 6,000 | 2,097,152 | 2,621,440 | 18,000 | 36,000 | 2 Gbps |
polar.mysql.g4.xlarge | 8 cores, 32 GB memory | 100 TB | 10,000 | 4,194,304 | 5,242,880 | 27,000 | 54,000 | 4 Gbps |
polar.mysql.g4.2xlarge | 16 cores, 64 GB memory | 100 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 4 Gbps |
polar.mysql.g6.2xlarge | 16 cores, 96 GB memory | 100 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.g8.2xlarge | 16 cores, 128 GB memory | 100 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
Dedicated
Node type | CPU and memory | Maximum storage capacity | Maximum number of connections1 (default) | Maximum number of inodes in the file system2 | Maximum number of blktags in the file system3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.mmx4.xlarge | 8 cores, 32 GB memory | 100 TB | 10,000 | 4,194,304 | 5,242,880 | 48,000 | 96,000 | 8 Gbps |
polar.mysql.mmx8.xlarge | 8 cores, 64 GB memory | 100 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 |
General-purpose
Node type | CPU and memory | Maximum storage capacity | Maximum number of connections1 (default) | Maximum number of inodes in the file system2 | Maximum number of blktags in the file system3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.mmg2.xlarge | 8 cores, 16 GB memory | 100 TB | 6,000 | 2,097,152 | 2,621,440 | 18,000 | 36,000 | 2 Gbps |
polar.mysql.mmg4.xlarge | 8 cores, 32 GB memory | 100 TB | 10,000 | 4,194,304 | 5,242,880 | 27,000 | 54,000 | 4 Gbps |
polar.mysql.mmg4.2xlarge | 16 cores, 64 GB memory | 100 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 4 Gbps |
polar.mysql.mmg6.2xlarge | 16 cores, 96 GB memory | 100 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.mmg8.2xlarge | 16 cores, 128 GB memory | 100 TB | 16,000 | 6,291,456 | 7,864,320 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.mmg4.4xlarge | 32 cores, 128 GB memory | 100 TB | 32,000 | 12,582,912 | 15,728,640 | 63,000 | 126,000 | 8 Gbps |
Note The maximum IOPS and I/O bandwidth of a PolarDB for MySQL Enterprise Edition cluster increase proportionally with the number of nodes. For example, in a PolarDB for MySQL Enterprise Edition cluster that uses dedicated specifications, 8-core 32 GB compute nodes, and PSL5 storage, the maximum storage performance of the cluster is 4 × 96,000 IOPS and 4 × 8 Gbps I/O bandwidth if the cluster contains one read-write node and three read-only nodes.
A PolarDB for MySQL 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. For heavy-load production environments, we recommend that you do not use PolarDB for MySQL clusters that have 2 cores and 8 GB of memory. For production environments, we recommend that you use PolarDB for MySQL clusters that have at least 8 cores and 32 GB of memory.
A global database network (GDN) does not support PolarDB for MySQL clusters of the following specifications: 2 cores and 4 GB of memory or 2 cores and 8 GB of memory.
Maximum number of connections1
The maximum number of connections described in the table is the default value. You can use the max_connections parameter to specify the maximum number of connections in the PolarDB console. Valid values: 1 to 200000. For information about how to modify cluster parameters, see Configure cluster and node parameters.
Maximum number of inodes in the file system2 and Maximum number of blktags in the file system3
PolarDB uses the self-developed distributed file system PolarFileSystem (PolarFS) to access the 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 number of inodes and the number of 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
Maximum IOPS4
The maximum IOPS indicates the theoretical limit. We cannot guarantee that the nominal values can be achieved in all scenarios.