Product specification
Cluster Edition and Multi-master Cluster (Limitless) support two specifications: General-purpose and Dedicated.
Dedicated: Each cluster has exclusive access to its allocated computing resources, such as CPUs, and does not share them with other clusters on the same server. This provides more stable and reliable performance.
General-purpose: Different clusters on the same server share idle computing resources, such as CPUs. This resource sharing provides better cost-effectiveness.
Compute node specifications
Cluster Edition
Dedicated
Specification code | CPU and memory | Maximum storage capacity | Default maximum connections1 | Maximum file system inodes2 | Maximum file system blktags3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.x4.medium | 2 cores, 8 GB | 100 TB | 6,000 | 20,971,520 | 26,214,400 | 8,000 | 16,000 | 1 Gbps |
polar.mysql.x8.medium | 2 cores, 16 GB | 100 TB | 8,000 | 20,971,520 | 26,214,400 | 18,000 | 36,000 | 2 Gbps |
polar.mysql.x4.large | 4 cores, 16 GB | 100 TB | 8,000 | 20,971,520 | 26,214,400 | 32,000 | 64,000 | 4 Gbps |
polar.mysql.x8.large | 4 cores, 32 GB | 100 TB | 8,000 | 20,971,520 | 26,214,400 | 36,000 | 72,000 | 4 Gbps |
polar.mysql.x4.xlarge | 8 cores, 32 GB | 100 TB | 10,000 | 20,971,520 | 26,214,400 | 48,000 | 96,000 | 8 Gbps |
polar.mysql.x8.xlarge | 8 cores, 64 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 50,000 | 108,000 | 10 Gbps |
polar.mysql.x4.2xlarge | 16 cores, 64 GB | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 50,000 | 192,000 | 16 Gbps |
polar.mysql.x8.2xlarge | 16 cores, 128 GB | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 50,000 | 192,000 | 16 Gbps |
polar.mysql.x4.4xlarge | 32 cores, 128 GB | 500 TB | 64,000 | 104,857,600 | 131,072,000 | 80,000 | 288,000 | 20 Gbps |
polar.mysql.x8.4xlarge | 32 cores, 256 GB | 500 TB | 64,000 | 104,857,600 | 131,072,000 | 80,000 | 288,000 | 24 Gbps |
polar.mysql.x8.8xlarge | 64 cores, 512 GB | 1 PB | 100,000 | 104,857,600 | 131,072,000 | 100,000 | 288,000 | 24 Gbps |
polar.mysql.x8.12xlarge | 88 cores, 710 GB | 1 PB | 100,000 | 104,857,600 | 131,072,000 | 150,000 | 384,000 | 32 Gbps |
polar.mysql.x8.15xlarge | 120 cores, 920 GB | 1 PB | 150,000 | 104,857,600 | 131,072,000 | 150,000 | 523,000 | - |
General-purpose
Specification code | CPU and memory | Maximum storage capacity | Default maximum connections1 | Maximum file system inodes2 | Maximum file system blktags3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.g2.medium | 2 cores, 4 GB | 100 TB | 1,800 | 20,971,520 | 26,214,400 | 4,000 | 8,000 | 1 Gbps |
polar.mysql.g4.medium | 2 cores, 8 GB | 100 TB | 2,000 | 20,971,520 | 26,214,400 | 8,000 | 16,000 | 1 Gbps |
polar.mysql.g2.large | 4 cores, 8 GB | 100 TB | 3,000 | 20,971,520 | 26,214,400 | 15,000 | 30,000 | 2 Gbps |
polar.mysql.g4.large | 4 cores, 16 GB | 100 TB | 6,000 | 20,971,520 | 26,214,400 | 21,000 | 42,000 | 2 Gbps |
polar.mysql.g2.xlarge | 8 cores, 16 GB | 100 TB | 6,000 | 20,971,520 | 26,214,400 | 24,000 | 48,000 | 2 Gbps |
polar.mysql.g4.xlarge | 8 cores, 32 GB | 100 TB | 10,000 | 20,971,520 | 26,214,400 | 27,000 | 54,000 | 4 Gbps |
polar.mysql.g4.2xlarge | 16 cores, 64 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 31,500 | 63,000 | 4 Gbps |
polar.mysql.g6.2xlarge | 16 cores, 96 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.g8.2xlarge | 16 cores, 128 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.g4.4xlarge | 32 cores, 128 GB | 500 TB | 32,000 | 104,857,600 | 131,072,000 | 42,000 | 84,000 | 8 Gbps |
Multi-master Cluster (Limitless)
Dedicated
Specification code | CPU and memory | Maximum storage capacity | Default maximum connections1 | Maximum file system inodes2 | Maximum file system blktags3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.mmx4.xlarge | 8 cores, 32 GB | 100 TB | 10,000 | 20,971,520 | 26,214,400 | 48,000 | 96,000 | 8 Gbps |
polar.mysql.mmx8.xlarge | 8 cores, 64 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 50,000 | 108,000 | 10 Gbps |
polar.mysql.mmx4.2xlarge | 16 cores, 64 GB | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 50,000 | 192,000 | 16 Gbps |
polar.mysql.mmx8.2xlarge | 16 cores, 128 GB | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 50,000 | 192,000 | 16 Gbps |
polar.mysql.mmx4.4xlarge | 32 cores, 128 GB | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 80,000 | 288,000 | 20 Gbps |
polar.mysql.mmx8.4xlarge | 32 cores, 256 GB | 100 TB | 64,000 | 20,971,520 | 26,214,400 | 80,000 | 288,000 | 24 Gbps |
polar.mysql.mmx8.8xlarge | 64 cores, 512 GB | 500 TB | 64,000 | 104,857,600 | 131,072,000 | 100,000 | 288,000 | 24 Gbps |
polar.mysql.mmx8.12xlarge | 88 cores, 710 GB | 500 TB | 100,000 | 104,857,600 | 131,072,000 | 150,000 | 384,000 | 32 Gbps |
General-purpose
Specification code | CPU and memory | Maximum storage capacity | Default maximum connections1 | Maximum file system inodes2 | Maximum file system blktags3 | PSL4 maximum IOPS4 | PSL5 maximum IOPS4 | I/O bandwidth |
polar.mysql.mmg2.xlarge | 8 cores, 16 GB | 100 TB | 6,000 | 20,971,520 | 26,214,400 | 24,000 | 48,000 | 2 Gbps |
polar.mysql.mmg4.xlarge | 8 cores, 32 GB | 100 TB | 10,000 | 20,971,520 | 26,214,400 | 27,000 | 54,000 | 4 Gbps |
polar.mysql.mmg4.2xlarge | 16 cores, 64 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 31,500 | 63,000 | 4 Gbps |
polar.mysql.mmg6.2xlarge | 16 cores, 96 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.mmg8.2xlarge | 16 cores, 128 GB | 100 TB | 16,000 | 20,971,520 | 26,214,400 | 31,500 | 63,000 | 8 Gbps |
polar.mysql.mmg4.4xlarge | 32 cores, 128 GB | 100 TB | 32,000 | 20,971,520 | 26,214,400 | 63,000 | 126,000 | 8 Gbps |
Note The maximum IOPS and I/O bandwidth of an Enterprise Edition cluster increase proportionally with the number of nodes. For example, if a cluster uses dedicated specifications, 8-core 32 GB compute nodes, and the PSL5 storage class, the total maximum storage performance for four nodes (one read/write node and three read-only nodes) is 4 × 96,000 IOPS and 4 × 8 Gbps.
Each sub-cluster in an Enterprise Edition cluster has independent storage specifications and is not affected by other sub-clusters.
Each node in an Enterprise Edition cluster has independent storage specifications and is not affected by other nodes. For example, if you purchase a cluster with a storage specification of 96,000 IOPS and 8 Gbps bandwidth, and the cluster has four nodes (one read/write node and three read-only nodes), each node has 96,000 IOPS and 8 Gbps of bandwidth. The performance of each node is not affected by the others.
A cluster with 2 cores and 8 GB of memory is suitable for entry-level applications. It is mainly used for testing, trials, and scenarios with very light payloads. This specification is not recommended for high-payload production environments. For production environments, use a cluster with 8 cores and 32 GB of memory or higher.
Clusters in a Global Database Network (GDN) do not support 2-core 4 GB or 2-core 8 GB node specifications.
PolarStore (PSL4/PSL5) supports petabyte-level storage. If you have this requirement, you can contact us to reserve resources.
Default maximum connections1
The maximum connections shown in the tables are the default values. You can adjust the actual maximum connections for your cluster by modifying the max_connections parameter in the console. The value of this parameter can range from 1 to 200,000. For more information, see Set cluster parameters.
Maximum file system inodes2 and Maximum file system blktags3
PolarDB uses its self-developed distributed file system, PolarFileSystem (PolarFS), to access underlying storage. Similar to traditional file systems, PolarFS also has inodes and blktags. An inode corresponds to a file, and a blktag corresponds to a 4 MB logical space on Elastic Block Storage. The number of inodes and blktags is linearly related to the disk capacity. For example, a 10 GB disk can have a maximum of 2,048 inodes and 2,560 blktags. If the capacity, number of inodes, or number of blktags reaches the specification limit, you must upgrade the specifications.
Capacity unit conversions:
1 TB = 1,024 GB
1 GB = 1,024 MB
1 MB = 1,024 KB
1 KB = 1,024 Bytes
Maximum IOPS4
The maximum IOPS is a theoretical value and is not guaranteed under all conditions.