This topic describes the specifications and pricing of PolarDB, including billing methods, billing items, and the prices of compute nodes, storage space, data backups, SQL Explorer, and global database networks (GDNs).
Billing methods
- Subscription
If you use the subscription billing method, you must pay for the compute nodes that you use when you create clusters. You are charged for the consumed storage space by hour. The charges are deducted from your account balance on an hourly basis.
- Pay-as-you-go (pay by hour)
If you use the pay-as-you-go billing method, you do not need to pay for clusters when you create the clusters. You need only to pay for the resources after you use them. You are charged for the compute codes and the consumed storage space by hour. The charges are deducted from your account balance on an hourly basis.
Billing items
| Billing item | Billing method |
|---|---|
| Compute node (a primary node and a read-only node) | This billing item uses the subscription or pay-as-you-go billing method. |
| Storage space | This billing item uses the pay-as-you-go billing method. |
| Data backup (You are billed for only the consumed storage space that exceeds the free quota.) | In PolarDB, the backup feature is available for free. Some storage space is provided for free to store the backup files. If the consumed storage space exceeds the free quota, you are billed for only the excess storage space. For more information, see Back up data. |
| SQL Explorer pricing (optional) | After you enable SQL Explorer, the pay-as-you-go billing method is used for this feature. For more information, see SQL Explorer. |
| GDN (optional) | The GDN feature is available for free. You are billed for only each PolarDB cluster that uses the GDN feature. For more information, see GDN. |
Specifications and pricing of compute nodes
- Specifications of compute nodes
All the nodes in PolarDB clusters are hosted on dedicated instances. The CPU, memory, storage, and I/O resources allocated to a node are exclusive to this node. This improves the stability and reliability of the node.
The following table lists the specifications of PolarDB nodes.
Table 1. PolarDB for MySQL node specifications Node type CPU and memory Maximum storage capacity Maximum number of connections Internal network bandwidth Maximum number of IOPS I/O bandwidth polar.mysql.s2.large 4 cores
8 GB
5 TB 1,200 1 Gbps 8,000 1 Gbps polar.mysql.x4.medium 2 cores
8 GB
5 TB 1,200 1 Gbps 8,000 1 Gbps polar.mysql.x4.large 4 cores
16 GB
10 TB 5,000 10 Gbps 32,000 4 Gbps polar.mysql.x4.xlarge 8 cores
32 GB
10 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
50 TB 20,000 10 Gbps 128,000 16 Gbps polar.mysql.x8.4xlarge 32 cores
256 GB
50 TB 64,000 10 Gbps 192,000 24 Gbps polar.mysql.x8.8xlarge 64 cores
512 GB
50TB 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 Note- A PolarDB cluster that has 2 CPU cores and 8 GB memory provides the basic specifications that are required in tests, trials, and other light load scenarios. We recommend that you do not use the clusters of this type in heavy-load production environments. In production environments, we recommend that you use a PolarDB cluster that has 8 CPU cores and 32 GB memory or higher specifications.
- You can select a node type for the primary node when you create a standard cluster. The same node type is automatically applied to read-only nodes.
- The maximum number of IOPS is a theoretically calculated 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 for the cluster does not change.
- Compute node pricing
Note
The following table lists the prices of a single node. By default, a standard PolarDB cluster consists of a primary node and a read-only node.
Table 2. Compute node pricing Parameter Mainland China China (Hong Kong) US (Silicon Valley) Singapore (Singapore) Indonesia (Jakarta) Malaysia (Kuala Lumpur) Germany (Frankfurt) India (Mumbai) US (Virginia) Japan (Tokyo) Node type CPU and memory polar.mysql.x4.medium 2 cores
8 GB
USD 44/month
USD 0.091/hour
USD 76/month
USD 0.117/hour
USD 62/month
USD 0.128 /hour
USD 76/month
USD 0.159 /hour
USD 74/month
USD 0.15/hour
USD 76/month
USD 0.159 /hour
USD 67/month
USD 0.139 /hour
USD 61 /month
USD 0.126 /hour
USD 50 /month
USD 0.104 /hour
USD 64 /month
USD 0.133 /hour
polar.mysql.x4.large Quad-core
16 GB
USD 155/month
USD 0.323/hour
USD 295/month
USD 0.532/hour
USD 240/month
USD 0.501 /hour
USD 295/month
USD 0.613 /hour
USD 271/month
USD 0.57/hour
USD 295/month
USD 0.613 /hour
USD 264/month
USD 0.549 /hour
USD 233 /month
USD 0.484 /hour
USD 202 /month
USD 0.42 /hour
USD 248 /month
USD 0.516 /hour
polar.mysql.x4.xlarge 8 cores
32 GB
USD 310/month
USD 0.646/hour
USD 589/month
USD 1.063/hour
USD 480/month
USD 1.001 /hour
USD 589/month
USD 1.226 /hour
USD 542/month
USD 1.13/hour
USD 589/month
USD 1.226 /hour
USD 527/month
USD 1.097 /hour
USD 480/month
USD 1 /hour
USD 403 /month
USD 0.839 /hour
USD 496/month
USD 1.032 /hour
polar.mysql.x8.xlarge 8 cores
64 GB
USD 496/month
USD 1.033/hour
USD 743/month
USD 1.342/hour
USD 620/month
USD 1.291 /hour
USD 743/month
USD 1.548 /hour
USD 689/month
USD 1.44/hour
USD 743/month
USD 1.548 /hour
USD 651/month
USD 1.355 /hour
USD 604 /month
USD 1.258 /hour
USD 496/month
USD 1.032 /hour
USD 635 /month
USD 1.323 /hour
polar.mysql.x8.2xlarge 16 cores
128 GB
USD 991/month
USD 2.064/hour
USD 1,486/month
USD 2.684/hour
USD 1,239/month
USD 2.58 /hour
USD 1,486/month
USD 3.096 /hour
USD 1,378/month
USD 2.87/hour
USD 1,486/month
USD 3.096 /hour
USD 1,301/month
USD 2.709 /hour
USD 1208 /month
USD 2.516 /hour
USD 991/month
USD 2.064/hour
USD 1270 /month
USD 2.645 /hour
polar.mysql.x8.4xlarge 32 cores
256 GB
USD 1,982/month
USD 4.128/hour
USD 2,972/month
USD 5.367/hour
USD 2,477/month
USD 5.16 /hour
USD 2,972/month
USD 6.192 /hour
USD 2,756/month
USD 5.74/hour
USD 2,972/month
USD 6.192 /hour
USD 2,601/month
USD 5.418 /hour
USD 2415 /month
USD 5.031 /hour
USD 1,982/month
USD 4.128/hour
USD 2539 /month
USD 5.289 /hour
polar.mysql.x8.12xlarge 88-core
710 GB
USD 5,449/month
USD 11.351/hour
USD 8,173/month
USD 14.756/hour
USD 6,811/month
USD 14.189 /hour
USD 8,173/month
USD 17.026 /hour
USD 7,577/month
USD 15.78/hour
USD 8,173/month
USD 17.026 /hour
USD 7,229/month
USD 15.059 /hour
USD 6640 /month
USD 10.061 /hour
USD 5,449/month
USD 11.351/hour
USD 6981 /month
USD 14.543 /hour
Storage pricing
- Pay-as-you-go
Storage resources are provisioned in a serverless architecture. Therefore, you do not need to specify the storage capacity when you create clusters. The storage capacity of the clusters is automatically increased when the amount of data increases. You are billed for only the storage space that you use. On the Overview page in the PolarDB console, you can view the storage space that you use.
- Mainland China: USD 0.00077/GB/hour.
- China (Hong Kong) and regions outside China: USD 0.00085/GB/hour.
Note The maximum storage capacity varies based on cluster specifications. If you use 90% of the storage space, the system sends SMS messages and emails to you on a daily basis. If you need to increase the maximum storage capacity, upgrade your cluster specifications. For more information, see Change the specifications of a cluster. - Storage packages
If you need to store large amounts of data, such as 1,000 GB data or more, storage packages are more cost-effective than the pay-as-you-go billing method. You are offered larger discounts for the storage packages that provide higher storage capacities. To purchase a storage package, visit the Apsara PolarDB (Storage Package) page.
Storage capacity (GB) Mainland China Outside Mainland China Pay-as-you-go (USD/month) Storage package (USD/month) Pay-as-you-go (USD/month) Storage package (USD/month) 100 56 55 (about 1.7% off)
62 61 (about 1.6% off)
200 112 109 (about 2.7% off)
124 121 (about 2.4% off)
300 168 163 (about 3.0% off)
186 182 (about 2.2% off)
500 280 271 (about 3.2% off)
310 302 (about 2.6% off)
1,000 560 490 (12.5% off)
620 550 (about 11.3% off)
2,000 1,120 980 (12.5% off)
1,240 1,090 (about 12.1% off)
3,000 1,680 1,210 (about 28.0% off)
1,860 1,340 (about 28.0% off)
5,000 2,800 2,020 (about 28.0% off)
3,100 2,230 (about 28.1% off)
10,000 5,600 3,260 (about 41.8% off)
6,200 3,630 (about 41.5% off)
20,000 11,200 6,510 (about 41.9% off)
12,400 7,250 (about 41.5% off)
30,000 16,800 9,760 (about 42.0% off)
18,600 10,870 (about 41.5% off)
50,000 28,000 14,860 (about 47.0% off)
31,000 16,550 (about 46.6% off)
100,000 56,000 29,720 (about 47.0% off)
62,000 33,110 (about 46.6% off)
Data backup pricing
The backup and restoration features of PolarDB are available for free. Backup files occupy some storage space. When you use the backup feature of PolarDB, you are billed based on the storage space and the storage duration of backup files. The backup files include data backup files and log backup files. For more information about how to configure the backup feature, see Back up data.
| Region | Level-1 backup | Level-2 backup | Log backup |
|---|---|---|---|
| Mainland China | USD 0.000464/GB/hour | USD 0.0000325/GB/hour | USD 0.0000325/GB/hour |
| Hong Kong (China) and regions outside China | USD 0.000650/GB/hour | USD 0.0000455/GB/hour | USD 0.0000455/GB/hour |
| Backup type | Free quota | Billing rule |
|---|---|---|
| Level-1 backups | Database storage usage × 50%
You can view the database storage usage of a cluster on the Overview page of the cluster in the PolarDB console. |
Storage fee per hour = (Total physical storage of level-1 backups - Free quota) ×
Unit price per hour
For example, if the total physical storage of level-1 backups is 700 GB and the database storage usage is 1,000 GB, the storage fee per hour is USD 0.0928. The storage fee is calculated based on the following formula: [700 GB - (1,000 GB × 50%)] × USD 0.000464 = USD 0.0928. |
| Level-2 backups | None | Storage fee per hour = Total physical storage of level-2 backups × Unit price per
hour
For example, if the total physical storage of level-2 backups is 1,000 GB, the storage fee per hour is USD 0.0325. The fee is calculated based on the following formula: 1,000 GB × USD 0.0000325 = USD 0.0325. |
| Log backups | 100GB | Storage fee per hour = (Total physical storage of log backups - 100 GB) × Unit price
per hour
For example, if the total physical storage of log backups is 1,000 GB, the storage fee per hour is USD 0.02925. The fee is calculated based on the following formula: (1,000 GB - 100 GB) × USD 0.0000325 = USD 0.02925. |
SQL Explorer pricing
You are billed based on the storage space that is consumed by audit logs.
- Mainland China: USD 0.0013/GB/hour.
- China (Hong Kong) and regions outside China: USD 0.0019/GB/hour.
GDN pricing
The GDN feature is available for free. You are billed for only each PolarDB cluster that uses the GDN feature. For more information about the prices of PolarDB clusters, see Specifications and pricing of compute nodes.
FAQ
- What is the price if I need to add a read-only node?
For a PolarDB cluster, a read-only node is charged at the same price as the primary node. For more information, see Specifications and pricing of compute nodes.
- Is the maximum storage capacity doubled after I add a read-only node?
No, PolarDB uses an architecture where computing is decoupled from storage. The read-only nodes that you purchased are used for computing. If you add read-only nodes to your cluster, the storage capacity of the cluster does not change.
Storage resources are provisioned in a serverless architecture. Therefore, you do not need to specify the storage capacity when you create clusters. The storage capacity of the clusters is automatically increased when the amount of data increases. You are billed for only the storage space that you use. The maximum storage capacity for each cluster varies based on the cluster specifications. If you need to increase the maximum storage capacity, upgrade your cluster specifications. For more information, see Change the specifications of a cluster.