This topic describes the specifications and pricing of PolarDB, including billing methods, billable 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 are used 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 are charged for the compute nodes and the consumed storage space of the clusters by hour. The charges are deducted from your account balance on an hourly basis.
Billable items
- The following table describes the billable items of PolarDB clusters.
Billable item Description Compute node (a primary node and a read-only node) This billable item uses the subscription or pay-as-you-go billing method. Storage space This billable item uses the pay-as-you-go billing method. Data backup (You are charged for only the consumed storage space that exceeds the free quota.) In PolarDB, the backup feature is free. You are charged for only the storage space that is used by backup files. For more information, see Back up data. SQL Explorer (optional) After you enable SQL Explorer, the pay-as-you-go billing method is used. For more information, see SQL Explorer. GDN (optional) The GDN feature is free. You are charged for only each PolarDB cluster that uses the GDN feature. For more information, see GDN. - The following figure shows the proportion of fees incurred by billable items in a
PolarDB cluster.
Specifications and pricing of compute nodes
- Specifications of compute nodes
All the node specifications of PolarDB for MySQL Cluster Edition are dedicated nodes. The dedicated nodes indicate that the CPU, memory, storage, and I/O resources that are allocated to the nodes are dedicated to these nodes and are not shared by other nodes. Therefore, the performance of the dedicated nodes is more stable and reliable.
PolarDB for MySQL Single Node adopts the node specification of the burstable performance type, and shares resources in a computing resource pool. This improves resource utilization. The Single Node architecture also saves resource costs because no proxy is required.
By default, PolarDB for MySQL Archive Database uses only one compute node that has dedicated computing specifications. This saves costs at the PolarProxy layer and overheads of synchronizing redo logs.
PolarDB provides the nodes of the following specifications for your choice.
Table 1. Specifications of compute nodes Product edition Node specification code CPU and memory Maximum storage capacity Maximum number of connections Internal bandwidth Maximum number of IOPS I/O bandwidth Cluster Edition 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 20 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 100 TB 20,000 10 Gbps 128,000 16 Gbps polar.mysql.x8.4xlarge 32 cores, 256 GB 100 TB 64,000 10 Gbps 192,000 24 Gbps polar.mysql.x8.8xlarge 64 cores, 512 GB 100 TB 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 Single Node polar.mysql.s2.large 4 cores, 8 GB 5 TB 1,200 1 Gbps 8,000 1 Gbps Archive Database polar.mysql.a4.xlarge 8 cores, 32 GB 100 TB 10,000 10 Gbps 64,000 8 Gbps Note- Clusters that have 2 cores and 8 GB are entry-level clusters, and are used in tests, trials, and 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 clusters that have at least 8 cores and 32 GB.
- You can select a node type for the primary node when you create a Cluster Edition cluster. The same node type is automatically applied to read-only nodes.
- The maximum number of input/output operations per second (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 does not change.
- Compute node pricing
Note
The following table describes the prices of a single node. By default, a Cluster Edition PolarDB cluster consists of a primary node and a read-only node.
Table 2. Prices of compute nodes Product edition Node specification code CPU and memory
Subscription price (monthly price) and pay-as-you-go price (hourly price) Mainland China US (Silicon Valley) Indonesia (Jakarta) Germany (Frankfurt) India (Mumbai) US (Virginia) Japan (Tokyo) China (Hong Kong), Singapore (Singapore), Malaysia (Kuala Lumpur), Australia (Sydney), and UK (London) Cluster Edition polar.mysql.x4.medium 2 cores, 8 GB
USD 44
USD 0.092
USD 62
USD 0.130
USD 74
USD 0.155
USD 67
USD 0.140
USD 61
USD 0.128
USD 50
USD 0.105
USD 64
USD 0.140
USD 76
USD 0.160
polar.mysql.x4.large 4 cores, 16 GB
USD 155
USD 0.323
USD 240
USD 0.500
USD 271
USD 0.565
USD 264
USD 0.550
USD 233
USD 0.486
USD 202
USD 0.421
USD 248
USD 0.520
USD 295
USD 0.620
polar.mysql.x4.xlarge 8 cores, 32 GB
USD 310
USD 0.646
USD 480
USD 1.000
USD 542
USD 1.129
USD 527
USD 1.098
USD 480
USD 1.000
USD 403
USD 0.840
USD 496
USD 1.040
USD 589
USD 1.230
polar.mysql.x8.xlarge 8 cores, 64 GB
USD 496
USD 1.033
USD 620
USD 1.292
USD 689
USD 1.436
USD 651
USD 1.356
USD 604
USD 1.258
USD 496
USD 1.033
USD 635
USD 1.330
USD 743
USD 1.550
polar.mysql.x8.2xlarge 16 cores, 128 GB
USD 991
USD 2.065
USD 1,239
USD 2.581
USD 1,378
USD 2.871
USD 1,301
USD 2.711
USD 1,208
USD 2.517
USD 991
USD 2.065
USD 1,270
USD 2.650
USD 1,486
USD 3.100
polar.mysql.x8.4xlarge 32 cores, 256 GB
USD 1,982
USD 4.129
USD 2,477
USD 5.161
USD 2,756
USD 5.742
USD 2,601
USD 5.419
USD 2,415
USD 5.031
USD 1,982
USD 4.129
USD 2,539
USD 5.290
USD 2,972
USD 6.200
polar.mysql.x8.8xlarge 64 cores, 512 GB
USD 3,963
USD 8.256
USD 4,953
USD 10.319
USD 5,511
USD 11.481
USD 5,722
USD 11.921
USD 5,313
USD 11.069
USD 4,360
USD 9.084
USD 5,586
USD 11.640
USD 5,944
USD 12.390
polar.mysql.x8.12xlarge 88 cores, 710 GB
USD 5,449
USD 11.352
USD 6,811
USD 14.190
USD 7,577
USD 15.786
USD 7,229
USD 15.061
USD 6,640
USD 13.833
USD 5,449
USD 11.352
USD 6,981
USD 14.550
USD 8,173
USD 17.030
Single Node polar.mysql.s2.large 4 cores, 8 GB
USD 44
USD 0.09
USD 65
USD 0.136
Archive Database polar.mysql.a4.xlarge 8 cores, 32 GB
USD 310
USD 0.646
USD 480
USD 1.000
USD 542
USD 1.129
USD 527
USD 1.098
USD 480
USD 1.000
USD 403
USD 0.840
USD 496
USD 1.040
USD 589
USD 1.230
Storage space pricing
- Pay-as-you-go
Storage space is provisioned in a serverless architecture. Therefore, you do not need to specify the storage capacity when you purchase clusters. The storage capacity of the clusters is automatically increased when the amount of data increases. You are charged for only the used storage space. On the Overview page of the clusters, you can view the used storage space.
- 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 maximum storage capacity, the system sends text messages and emails to you on a daily basis. To increase the maximum storage capacity, upgrade your cluster specifications. For more information, see Change cluster configurations. - Storage plans
If you need to store a large amount of data, such as 1,000 GB of data or more, storage plans are more cost-effective than the pay-as-you-go billing method. Higher discounts are offered for the storage plans that provide larger storage capacities. For more information, see Purchase a storage plan.
Capacity (GB) Mainland China China (Hong Kong) and regions outside China Without storage plans (USD/month) Storage plan (USD/month) Without storage plans (USD/month) Storage plan (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 (about 12.5% off)
620 550 (about 11.3% off)
2,000 1,120 980 (about 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 (beyond the free quota)
The backup and restoration features of PolarDB are free. Backup files occupy some storage space. When you use the backup feature of PolarDB, you are charged based on the used storage space and the storage duration of backup files. The backup files are 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 method |
|---|---|---|
| Level-1 backups | Used database storage space × 50%
You can view the used database storage space on the Overview page in the 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 (snapshots) is 700 GB and the used database storage space is 1,000 GB, the storage fee per hour is USD 0.0928. The 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 | 100 GB | 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 (optional)
You are charged for SQL Explorer based on the storage space that is occupied by audit logs.
- Mainland China: USD 0.0013/GB/hour.
- China (Hong Kong) and regions outside China: USD 0.0019/GB/hour.
GDN pricing (optional)
The GDN feature is free. You are charged for only each PolarDB cluster that uses the GDN feature. For more information about the pricing of PolarDB clusters, see Specifications and pricing of compute nodes.
FAQ
- What is the price if I add a read-only node?
The price of a read-only node is the same as that of the primary node. For more information, see Specifications and pricing of compute nodes.
- Is the storage capacity doubled after I add a read-only node?
No, the storage capacity is not doubled after you add a read-only node. PolarDB uses an architecture where computing is decoupled from storage. The read-only nodes that you purchase are computing resources. Therefore, the storage capacity is not increased.
Storage space is provisioned in a serverless architecture. Therefore, you do not need to specify the storage capacity when you purchase clusters. The storage capacity of the clusters is automatically increased when the amount of data increases. You are charged for only the used storage space. The maximum storage capacity for each cluster varies based on the cluster specifications. To increase the maximum storage capacity, upgrade your cluster specifications. For more information, see Upgrade cluster specifications.