ApsaraDB PolarDB MySQL-compatible edition provides three different editions:Cluster Edition, Single Node, and Archive Database. Each edition provides different specifications of compute nodes.

The following sections describe the specifications of compute nodes in different ApsaraDB PolarDB MySQL-compatible edition editions:

  • A Cluster Edition cluster 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.
  • A Single Node cluster uses nodes of the burstable performance type and shares resources in a computing resource pool. This improves resource usage. The Single Node architecture also reduces resource costs because no proxy is required.
  • By default, a Archive Database cluster uses one dedicated node. This reduces the expenses on PolarProxy and the overheads of synchronizing redo logs.
Table 1. Specifications of compute nodes
Edition Node specification code CPU and memory Maximum storage capacity Maximum number of concurrent connections Internal bandwidth Maximum IOPS I/O bandwidth
Cluster Edition (Dedicated) polar.mysql.x4.medium 2 cores and 8 GB 5 TB 2,000 1 Gbps 8,000 1 Gbps
polar.mysql.x4.large 4 cores and 16 GB 10 TB 8,000 10 Gbps 32,000 4 Gbps
polar.mysql.x4.xlarge 8 cores and 32 GB 20 TB 10,000 10 Gbps 64,000 8 Gbps
polar.mysql.x8.xlarge 8 cores and 64 GB 30 TB 10,000 10 Gbps 72,000 10 Gbps
polar.mysql.x8.2xlarge 16 cores and 128 GB 100 TB 20,000 10 Gbps 128,000 16 Gbps
polar.mysql.x8.4xlarge 32 cores and 256 GB 100 TB 64,000 10 Gbps 192,000 24 Gbps
polar.mysql.x8.8xlarge 64 cores and 512 GB 100 TB 64,000 10 Gbps 192,000 24 Gbps
polar.mysql.x8.12xlarge 88 cores and 710 GB 100 TB 64,000 25 Gbps 256,000 32 Gbps
Cluster Edition (General-purpose) polar.mysql.g2.medium 2 cores and 4 GB 5 TB 1,800 1 Gbps 4,000 1 Gbps
polar.mysql.g4.medium 2 cores and 8 GB 5 TB 2,000 1 Gbps 8,000 1 Gbps
polar.mysql.g2.large 4 cores and 8 GB 10 TB 3,000 10 Gbps 15,000 2 Gbps
polar.mysql.g4.large 4 cores and 16 GB 10 TB 6,000 10 Gbps 21,000 2 Gbps
polar.mysql.g2.xlarge 8 cores and 16 GB 10 TB 6,000 10 Gbps 24,000 2 Gbps
polar.mysql.g4.xlarge 8 cores and 32 GB 20 TB 10,000 10 Gbps 36,000 4 Gbps
polar.mysql.g4.2xlarge 16 cores and 64 GB 30 TB 16,000 10 Gbps 42,000 4 Gbps
Single node polar.mysql.s2.large 4 cores and 8 GB 5 TB 1,200 1 Gbps 8,000 1 Gbps
Archive database polar.mysql.a4.large 4 cores and 16 GB 50 TB 8,000 10 Gbps 32,000 4 Gbps
polar.mysql.a4.xlarge 8 cores and 32 GB 100 TB 10,000 10 Gbps 64,000 8 Gbps
polar.mysql.a8.xlarge 8 cores and 64 GB 100 TB 10,000 10 Gbps 72,000 10 Gbps
polar.mysql.a8.2xlarge 16 cores and 128 GB 100 TB 20,000 10 Gbps 128,000 16 Gbps
polar.mysql.a8.4xlarge 32 cores and 256 GB 100 TB 64,000 10 Gbps 192,000 24 Gbps
polar.mysql.a8.8xlarge 64 cores and 512 GB 100 TB 64,000 10 Gbps 192,000 24 Gbps
polar.mysql.a8.12xlarge 88 cores and 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 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 specify specifications of primary nodes when you create a Cluster Edition cluster. The same node specifications are automatically applied to read-only nodes.
  • The maximum 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.