A computing power plan is a prepaid resource plan offered by ApsaraDB for RDS. It can be used to offset the cost of pay-as-you-go computing resources for instances of . You are not billed for resources covered by the plan. You are billed hourly only for usage that exceeds the plan's quota. This topic describes the billing rules for computing power plans and how to purchase them.
Use cases
For large or fluctuating workloads, we recommend combining the Pay-As-You-Go billing method with a compute pack. This combination is more cost-effective than Pay-As-You-Go alone and more flexible than a Subscription.
Example scenarios:
-
Scenario 1: You need to explore and test various RDS instances for a few days.
For short-term use, a Subscription is unsuitable. Purchase a single compute pack to cover the costs of multiple Pay-As-You-Go instances and release them when you are finished. This approach is convenient, flexible, and more cost-effective than using Pay-As-You-Go alone.
-
Scenario 2: Your workload is expected to fluctuate significantly over the next six months, and the timing of peak usage is unpredictable. You need to adjust instance configurations or add more instances to handle these peaks.
For long-term, high-volume usage, Pay-As-You-Go alone can be expensive. Pairing a compute pack with your Pay-As-You-Go instances lowers costs while retaining their convenience and flexibility.
Notes
-
Only Alibaba Cloud accounts can purchase Compute Packages.
-
Pricing is subject to the details on the purchase page.
-
Compute Packages are currently available only in the following regions:
China (Hangzhou), China (Shanghai), China (Nanjing), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), and China (Chengdu).
-
Unused resources in a Compute Package expire at the end of its validity period.
-
You can purchase multiple Compute Packages, and their benefits are cumulative. Compute Packages cannot be renewed, upgraded, or downgraded.
NoteIf you purchase multiple Compute Packages, the one that expires first is used first.
-
Compute Packages are non-refundable.
-
If you have both an RDS Savings Plan and an RDS Compute Package, the RDS Compute Package is applied first.
Applicable resources
|
Applicable resource |
Description |
|
pay-as-you-go primary instance |
Offsets the compute resources for an RDS pay-as-you-go primary instance. |
|
pay-as-you-go read-only instance |
Offsets the compute resources for an RDS pay-as-you-go read-only instance. |
|
database proxy |
Offsets compute resources for the database proxy on pay-as-you-go or subscription RDS primary instances. |
subscription, pay-as-you-go, and serverless are three distinct billing methods. A resource plan applies offsets only as described above. For example, a resource plan offsets the compute resources for a pay-as-you-go instance, but not for a serverless instance or the storage resources of a pay-as-you-go instance.
Deduction rules
|
Rule |
Description |
|
Deduction method |
During the validity period of a Compute Package, units are deducted hourly based on the instance types and the number of database proxies you use.
Note
A Compute Package is measured in units. The number of units consumed per hour depends on the engine and instance type of the pay-as-you-go instance, and the number of database proxies. For details, see Compute Package unit consumption details. |
|
Deduction priority |
|
Compute plan examples
Scenario 1
Suppose you have an RDS MySQL instance with the instance type code mysql.n1.micro.1 (1 vCPU, 1 GB) in your account. You purchase a 1-year Compute Plan that provides 10 units.
The plan applies as follows:
-
A
mysql.n1.micro.1instance consumes 0.0015 units per hour. The 10-unit Compute Plan covers usage for approximately10 units ÷ 0.0015 units/hour ≈ 6,666 hours.Note-
The system rounds the result down to the nearest whole hour.
-
To see the hourly unit consumption for each pay-as-you-go instance type, see Details of Unit Consumption for Compute Plans.
-
-
6,666 hours is approximately
9 months, 7 days, and 18 hours. Once the Compute Plan's units are depleted, the instance reverts to pay-as-you-go billing.
Scenario 2
Suppose you have an RDS MySQL instance with the instance type code mysql.n1.micro.1 (1 vCPU, 1 GB) and an RDS PostgreSQL instance with the instance type code pg.n2.2c.1m (2 vCPUs, 4 GB) in your account. You purchase a 1-year Compute Plan that provides 10 units.
The plan applies as follows:
-
The
mysql.n1.micro.1instance type consumes 0.0015 units per hour, and thepg.n2.2c.1minstance type consumes 0.0093 units per hour. The two instances consume a combined total of0.0015 units + 0.0093 units = 0.0108 unitsper hour. -
The 10-unit Compute Plan covers usage for approximately
10 units ÷ 0.0108 units/hour ≈ 925 hours. -
925 hours is approximately
1 month, 8 days, and 13 hours. Once the Compute Plan's units are depleted, the instances revert to pay-as-you-go billing.
Purchase an RDS compute package
-
Go to the RDS buy page.
-
For Billing Method, select Compute Plan.
-
Select a Region and a Compute Plan Capacity.
Parameter
Description
Region
The compute package is available only in the following regions and can be used in any of them:
China (Hangzhou), China (Shanghai), China (Nanjing), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), and China (Chengdu).
Compute Plan Capacity
You can purchase a compute package with a capacity ranging from 5 to 10,000 units.
The larger the capacity you purchase, the greater the discount:
-
5 to 499 units: 10% discount.
-
500 to 4,999 units: 15% discount.
-
5,000 to 10,000 units: 20% discount.
-
-
Set the Subscription Duration and Quantity, and click Buy Now.
The following options are available:
-
Subscription duration: You can purchase a compute package for one or two years. Unused units expire when the subscription ends.
-
Quantity: You can purchase multiple compute packages and use them together.
-
-
Review the service agreement and click Agree and Place Order.
Computing package usage details
-
Log in to Expenses & Costs.
-
In the navigation pane on the left, choose account > resource package.
-
On the resource package page, set resource dimension to resource package.
-
On the instance summary tab, you can view the total and remaining amounts for the resource package (the product name is rds_cuudr_dp_cn).
-
Click the usage details tab to view the deduction details for the resource package (the product name is rds_cuudr_dp_cn).
The remaining amount before deduction, deduction amount, and remaining amount after deduction columns show the deduction details for each resource package instance.
Resource plan consumption
The following credit consumption figures are for reference only. Your actual credit consumption is based on the usage details of your resource plan.
Use the following formulas to calculate credit consumption: Monthly credit consumption = Hourly credit consumption × 24 × days in the month and Yearly credit consumption = Hourly credit consumption × 24 × days in the year. These calculations assume a 30-day month and a 365-day year.
Database proxy
The following table shows consumption units per proxy.
|
Region |
Hourly units |
Monthly units |
Yearly units |
|
China (Hangzhou), China (Shanghai), China (Nanjing) - Local Region, China (Qingdao), China (Beijing), China (Hohhot), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu) |
0.0318 |
22.896 |
278.568 |
|
China (Zhangjiakou), China (Ulanqab) |
0.022 |
15.84 |
192.72 |
PostgreSQL instance specifications
-
primary instance
-
standard specifications (formerly x86 architecture)
Primary instance's cloud disk usage details
Series
Instance family
Specification code
CPU and memory
Credits/hour
Credits/month
Credits/year
Basic series
general purpose
pg.n2.2c.1m
2 cores, 4 GB
0.0093
6.696
81.468
pg.n4.2c.1m
2 cores, 8 GB
0.0113
8.136
98.988
pg.n2.4c.1m
4 cores, 8 GB
0.0217
15.624
190.092
pg.n4.4c.1m
4 cores, 16 GB
0.0286
20.592
250.536
pg.n4.6c.1m
6 cores, 24 GB
0.0429
30.888
375.804
pg.n4.8c.1m
8 cores, 32 GB
0.0571
41.112
500.196
pg.n2.small.1 (discontinued)
1 core, 2 GB
0.0037
2.664
32.412
pg.n2.medium.1 (to be discontinued)
2 cores, 4 GB
0.0093
6.696
81.468
pg.n4.medium.1 (to be discontinued)
2 cores, 8 GB
0.0113
8.136
98.988
pg.n2.large.1 (to be discontinued)
4 cores, 8 GB
0.0217
15.624
190.092
pg.n4.large.1 (to be discontinued)
4 cores, 16 GB
0.0286
20.592
250.536
pg.n2.xlarge.1 (to be discontinued)
8 cores, 16 GB
0.0435
31.32
381.06
pg.n4.xlarge.1 (to be discontinued)
8 cores, 32 GB
0.0571
41.112
500.196
pg.n2.2xlarge.1 (to be discontinued)
16 cores, 32 GB
0.0854
61.488
748.104
pg.n4.2xlarge.1 (to be discontinued)
16 cores, 64 GB
0.1154
83.088
1010.904
pg.n8.2xlarge.1 (to be discontinued)
16 cores, 128 GB
0.1477
106.344
1293.852
pg.n4.4xlarge.1 (to be discontinued)
32 cores, 128 GB
0.2309
166.248
2022.684
pg.n8.4xlarge.1 (to be discontinued)
32 cores, 256 GB
0.2951
212.472
2585.076
pg.n4.8xlarge.1 (discontinued)
64 cores, 256 GB
0.4529
326.088
3967.404
pg.n8.8xlarge.1 (discontinued)
64 cores, 512 GB
0.5797
417.384
5078.172
dedicated
pg.x8.medium.1
2 cores, 16 GB
0.0226
16.272
197.976
pg.x8.large.1
4 cores, 32 GB
0.0448
32.256
392.448
pg.x8.xlarge.1
8 cores, 64 GB
0.0889
64.008
778.764
pg.x4.2xlarge.1
16 cores, 64 GB
0.138
99.36
1208.88
pg.x8.2xlarge.1
16 cores, 128 GB
0.1764
127.008
1545.264
pg.x4.4xlarge.1
32 cores, 128 GB
0.2701
194.472
2366.076
pg.x8.4xlarge.1
32 cores, 256 GB
0.3502
252.144
3067.752
high availability series
general purpose
pg.n2.2c.2m
2 cores, 4 GB
0.0297
21.384
260.172
pg.n2.4c.2m
4 cores, 8 GB
0.0561
40.392
491.436
pg.n2.8c.2m
8 cores, 16 GB
0.1122
80.784
982.872
pg.n4.2c.2m
2 cores, 8 GB
0.036
25.92
315.36
pg.n4.4c.2m
4 cores, 16 GB
0.072
51.84
630.72
pg.n4.6c.2m
6 cores, 24 GB
0.0987
71.064
864.612
pg.n4.8c.2m
8 cores, 32 GB
0.144
103.68
1261.44
pg.n4.12c.2m
12 cores, 48 GB
0.2117
152.424
1854.492
dedicated
pg.x2.medium.2c
2 cores, 4 GB
0.0327
23.544
286.452
pg.x4.medium.2c
2 cores, 8 GB
0.0417
30.024
365.292
pg.x8.medium.2c
2 cores, 16 GB
0.053
38.16
464.28
pg.x2.large.2c
4 cores, 8 GB
0.0654
47.088
572.904
pg.x4.large.2c
4 cores, 16 GB
0.0829
59.688
726.204
pg.x8.large.2c
4 cores, 32 GB
0.1052
75.744
921.552
pg.x2.xlarge.2c
8 cores, 16 GB
0.13
93.6
1138.8
pg.x4.xlarge.2c
8 cores, 32 GB
0.1646
118.512
1441.896
pg.x8.xlarge.2c
8 cores, 64 GB
0.209
150.48
1830.84
pg.x2.3large.2c
12 cores, 24 GB
0.195
140.4
1708.2
pg.x4.3large.2c
12 cores, 48 GB
0.2451
176.472
2147.076
pg.x8.3large.2c
12 cores, 96 GB
0.3112
224.064
2726.112
pg.x2.2xlarge.2c
16 cores, 32 GB
0.2582
185.904
2261.832
pg.x4.2xlarge.2c
16 cores, 64 GB
0.3246
233.712
2843.496
pg.x8.2xlarge.2c
16 cores, 128 GB
0.4149
298.728
3634.524
pg.x4.3xlarge.2c
24 cores, 96 GB
0.4834
348.048
4234.584
pg.x8.3xlarge.2c
24 cores, 192 GB
0.6178
444.816
5411.928
pg.x2.4xlarge.2c
32 cores, 64 GB
0.5129
369.288
4493.004
pg.x4.4xlarge.2c
32 cores, 128 GB
0.6354
457.488
5566.104
pg.x8.4xlarge.2c
32 cores, 256 GB
0.8238
593.136
7216.488
pg.x2.13large.2c
52 cores, 96 GB
0.8277
595.944
7250.652
pg.x4.13large.2c
52 cores, 192 GB
1.0251
738.072
8979.876
pg.x8.13large.2c
52 cores, 384 GB
1.3091
942.552
11467.72
pg.x2.8xlarge.2c
64 cores, 128 GB
1.0116
728.352
8861.616
pg.x4.8xlarge.2c
64 cores, 256 GB
1.2617
908.424
11052.49
pg.x8.8xlarge.2c
64 cores, 512 GB
1.6112
1160.064
14114.11
pg.x2.13xlarge.2c
104 cores, 192 GB
1.6322
1175.184
14298.07
pg.x4.13xlarge.2c
104 cores, 384 GB
2.0206
1454.832
17700.46
pg.x8.13xlarge.2c
104 cores, 768 GB
2.5788
1856.736
22590.29
Intel SGX Security Enhanced
pg.x4t.medium.2c
2 cores, 8 GB
encrypted memory: 4 GB
0.05
36
438
pg.x4t.large.2c
4 cores, 16 GB
encrypted memory: 8 GB
0.0994
71.568
870.744
pg.x4t.xlarge.2c
8 cores, 32 GB
encrypted memory: 16 GB
0.1974
142.128
1729.224
pg.x4t.2xlarge.2c
16 cores, 64 GB
encrypted memory: 32 GB
0.3894
280.368
3411.144
pg.x4t.4xlarge.2c
32 cores, 128 GB
encrypted memory: 64 GB
0.7625
549
6679.5
SCU consumption for high-performance local disk primary instances
Series
Instance family
Instance type code
CPU and memory
SCUs per hour
SCUs per month
SCUs per year
high-availability series
general purpose
rds.pg.s2.large
2 cores, 4 GB
0.0297
21.384
260.172
rds.pg.s3.large
4 cores, 8 GB
0.0566
40.752
495.816
rds.pg.c1.large
8 cores, 16 GB
0.1071
77.112
938.196
rds.pg.c1.xlarge
8 cores, 32 GB
0.1966
141.552
1722.216
rds.pg.c2.xlarge
16 cores, 64 GB
0.3869
278.568
3389.244
dedicated (memory-optimized)
pg.x8.medium.2
2 cores, 16 GB
0.0983
70.776
861.108
pg.x8.large.2
4 cores, 32 GB
0.1934
139.248
1694.184
pg.x8.xlarge.2
8 cores, 64 GB
0.3811
274.392
3338.436
pg.x8.2xlarge.2
16 cores, 128 GB
0.762
548.64
6675.12
dedicated (compute-optimized)
pg.x4.large.2
4 cores, 16 GB
0.1251
90.072
1095.876
pg.x4.xlarge.2
8 cores, 32 GB
0.2443
175.896
2140.068
pg.x4.2xlarge.2
16 cores, 64 GB
0.4763
342.936
4172.388
pg.x4.4xlarge.2
32 cores, 128 GB
0.9526
685.872
8344.776
dedicated physical server
rds.pg.st.h43
60 cores, 470 GB
3.1549
2271.528
27636.92
Unit consumption for legacy specifications
Specification code
CPU cores
Memory
Units per hour
Units per month
Units per year
rds.pg.t1.small
1
1 GB
0.0083
5.976
72.708
pg.n1.micro.1
1
1 GB
0.0015
1.08
13.14
pg.gn5i-c2g1.large.1
2
8 GB
0.1866
134.352
1634.616
pg.gn5i-c4g1.xlarge.1
4
16 GB
0.208
149.76
1822.08
pg.gn5i-c8g1.2xlarge.1
8
32 GB
0.25
180
2190
pg.gn5i-c16g1.4xlarge.1
16
64 GB
0.3351
241.272
2935.476
pg.gn5i-c16g1.8xlarge.1
32
128 GB
0.6697
482.184
5866.572
pg.gn5i-c28g1.14xlarge.1
56
224 GB
0.9229
664.488
8084.604
pg.n2.small.2c
1
2 GB
0.0119
8.568
104.244
pg.n2.medium.2c
2
4 GB
0.0297
21.384
260.172
rds.pg.s1.small
1
2 GB
0.0154
11.088
134.904
pg.n2.small.1
1
2 GB
0.0037
2.664
32.412
pg.n4.8xlarge.1
64
256 GB
0.4529
326.088
3967.404
pg.n8.8xlarge.1
64
512 GB
0.5797
417.384
5078.172
-
Yitian Edition (ARM architecture) specifications
Consumption units for primary instances
Series
Instance family
Instance type
CPU and memory
Units per hour
Units per month
Units per year
high-availability series
general purpose
pg.n4m.2c.2m
2-core 8 GB
0.0226
16.272
197.976
pg.n4m.4c.2m
4-core 16 GB
0.0448
32.256
392.448
pg.n4m.8c.2m
8-core 32 GB
0.0892
64.224
781.392
pg.n2m.2c.2m
2-core 4 GB
0.0152
10.944
133.152
pg.n2m.4c.2m
4-core 8 GB
0.03
21.6
262.8
pg.n2m.8c.2m
8-core 16 GB
0.0597
42.984
522.972
dedicated
pg.x2m.medium.2c
2-core 4 GB
0.0208
14.976
182.208
pg.x4m.medium.2c
2-core 8 GB
0.0312
22.464
273.312
pg.x8m.medium.2c
2-core 16 GB
0.0423
30.456
370.548
pg.x2m.large.2c
4-core 8 GB
0.0416
29.952
364.416
pg.x4m.large.2c
4-core 16 GB
0.0623
44.856
545.748
pg.x8m.large.2c
4-core 32 GB
0.0845
60.84
740.22
pg.x2m.xlarge.2c
8-core 16 GB
0.0832
59.904
728.832
pg.x4m.xlarge.2c
8-core 32 GB
0.1245
89.64
1090.62
pg.x8m.xlarge.2c
8-core 64 GB
0.1689
121.608
1479.564
pg.x2m.2xlarge.2c
16-core 32 GB
0.1662
119.664
1455.912
pg.x4m.2xlarge.2c
16-core 64 GB
0.2490
179.28
2181.24
pg.x8m.2xlarge.2c
16-core 128 GB
0.3376
243.072
2957.376
pg.x2m.4xlarge.2c
32-core 64 GB
0.3322
239.184
2910.072
pg.x4m.4xlarge.2c
32-core 128 GB
0.4979
358.488
4361.604
pg.x8m.4xlarge.2c
32-core 256 GB
0.6753
486.216
5915.628
pg.x2m.8xlarge.2c
64-core 128 GB
0.6644
478.368
5820.144
pg.x4m.8xlarge.2c
64-core 256 GB
0.9957
716.904
8722.332
pg.x8m.8xlarge.2c
64-core 512 GB
1.3505
972.36
11830.38
-
-
read-only instance
-
Standard edition specifications (formerly X86 architecture)
Read-only instance consumption units
Instance family
Instance type
CPU and memory
Units per hour
Units per month
Units per year
General purpose
pgro.n2.2c.1m
2 cores, 4 GB
0.0149
10.728
130.524
pgro.n2.4c.1m
4 cores, 8 GB
0.0281
20.232
246.156
pgro.n2.8c.1m
8 cores, 16 GB
0.0562
40.464
492.312
pgro.n4.2c.1m
2 cores, 8 GB
0.018
12.96
157.68
pgro.n4.4c.1m
4 cores, 16 GB
0.036
25.92
315.36
pgro.n4.8c.1m
8 cores, 32 GB
0.072
51.84
630.72
Dedicated
pgro.x2.medium.1c
2 cores, 4 GB
0.0163
11.736
142.788
pgro.x2.large.1c
4 cores, 8 GB
0.0326
23.472
285.576
pgro.x2.xlarge.1c
8 cores, 16 GB
0.0649
46.728
568.524
pgro.x2.3large.1c
12 cores, 24 GB
0.0974
70.128
853.224
pgro.x2.2xlarge.1c
16 cores, 32 GB
0.1291
92.952
1130.916
pgro.x2.3xlarge.1c
24 cores, 48 GB
0.1937
139.464
1696.812
pgro.x2.4xlarge.1c
32 cores, 64 GB
0.2563
184.536
2245.188
pgro.x2.13large.1c
52 cores, 96 GB
0.4137
297.864
3624.012
pgro.x2.8xlarge.1c
64 cores, 128 GB
0.5057
364.104
4429.932
pgro.x2.13xlarge.1c
104 cores, 192 GB
0.8157
587.304
7145.532
pgro.x4.medium.1c
2 cores, 8 GB
0.0209
15.048
183.084
pgro.x4.large.1c
4 cores, 16 GB
0.0414
29.808
362.664
pgro.x4.xlarge.1c
8 cores, 32 GB
0.0823
59.256
720.948
pgro.x4.3large.1c
12 cores, 48 GB
0.1226
88.272
1073.976
pgro.x4.2xlarge.1c
16 cores, 64 GB
0.1623
116.856
1421.748
pgro.x4.3xlarge.1c
24 cores, 96 GB
0.2417
174.024
2117.292
pgro.x4.4xlarge.1c
32 cores, 128 GB
0.3177
228.744
2783.052
pgro.x4.13large.1c
52 cores, 192 GB
0.5123
368.856
4487.748
pgro.x4.8xlarge.1c
64 cores, 256 GB
0.6306
454.032
5524.056
pgro.x4.13xlarge.1c
104 cores, 384 GB
1.01
727.2
8847.6
pgro.x8.medium.1c
2 cores, 16 GB
0.0266
19.152
233.016
pgro.x8.large.1c
4 cores, 32 GB
0.0526
37.872
460.776
pgro.x8.xlarge.1c
8 cores, 64 GB
0.1046
75.312
916.296
pgro.x8.3large.1c
12 cores, 96 GB
0.1554
111.888
1361.304
pgro.x8.2xlarge.1c
16 cores, 128 GB
0.2074
149.328
1816.824
pgro.x8.3xlarge.1c
24 cores, 192 GB
0.3089
222.408
2705.964
pgro.x8.4xlarge.1c
32 cores, 256 GB
0.4117
296.424
3606.492
pgro.x8.13large.1c
52 cores, 384 GB
0.6543
471.096
5731.668
pgro.x8.8xlarge.1c
64 cores, 512 GB
0.8051
579.672
7052.676
pgro.x8.13xlarge.1c
104 cores, 768 GB
1.2889
928.008
11290.76
CU consumption details for read-only instances with high-performance local disks
Instance family
Instance type
vCPU and memory
CUs per hour
CUs per month
CUs per year
memory-optimized
pg.x8.xlarge.2
8 vCPUs, 64 GB
0.3811
274.392
3338.436
pg.x8.2xlarge.2
16 vCPUs, 128 GB
0.762
548.64
6675.12
compute-optimized
pg.x4.xlarge.2
8 vCPUs, 32 GB
0.2443
175.896
2140.068
pg.x4.2xlarge.2
16 vCPUs, 64 GB
0.4763
342.936
4172.388
pg.x4.4xlarge.2
32 vCPUs, 128 GB
0.9526
685.872
8344.776
dedicated host
rds.pg.st.h43
60 vCPUs, 470 GB
3.1549
2271.528
27636.92
Consumption units for historical read-only instances
Specification code
CPU cores
Memory
Hourly CU consumption
Monthly CU consumption
Annual CU consumption
pgro.n2.small.1c
1
2 GB
0.006
4.32
52.56
pgro.n2.medium.1c
2
4 GB
0.0149
10.728
130.524
-
Yitian instance specifications
Read-only instance units
Instance family
Type
CPU and memory
Units per hour
Units per month
Units per year
general purpose
pgro.n2m.2c.1m
2-core 4 GB
0.0078
5.616
68.328
pgro.n2m.4c.1m
4-core 8 GB
0.0154
11.088
134.904
pgro.n2m.8c.1m
8-core 16 GB
0.0308
22.176
269.808
pgro.n4m.2c.1m
2-core 8 GB
0.0114
8.208
99.864
pgro.n4m.4c.1m
4-core 16 GB
0.0225
16.2
197.1
pgro.n4m.8c.1m
8-core 32 GB
0.0447
32.184
391.572
dedicated
pgro.x2m.medium.1c
2-core 4 GB
0.0105
7.56
91.98
pgro.x2m.large.1c
4-core 8 GB
0.0208
14.976
182.208
pgro.x2m.xlarge.1c
8-core 16 GB
0.0416
29.952
364.416
pgro.x2m.2xlarge.1c
16-core 32 GB
0.0831
59.832
727.956
pgro.x2m.4xlarge.1c
32-core 64 GB
0.1662
119.664
1455.912
pgro.x2m.8xlarge.1c
64-core 128 GB
0.3322
239.184
2910.072
pgro.x4m.medium.1c
2-core 8 GB
0.0156
11.232
136.656
pgro.x4m.large.1c
4-core 16 GB
0.0312
22.464
273.312
pgro.x4m.xlarge.1c
8-core 32 GB
0.0623
44.856
545.748
pgro.x4m.2xlarge.1c
16-core 64 GB
0.1245
89.64
1090.62
pgro.x4m.4xlarge.1c
32-core 128 GB
0.2490
179.28
2181.24
pgro.x4m.8xlarge.1c
64-core 256 GB
0.4979
358.488
4361.604
pgro.x8m.medium.1c
2-core 16 GB
0.0212
15.264
185.712
pgro.x8m.large.1c
4-core 32 GB
0.0423
30.456
370.548
pgro.x8m.xlarge.1c
8-core 64 GB
0.0845
60.84
740.22
pgro.x8m.2xlarge.1c
16-core 128 GB
0.1689
121.608
1479.564
pgro.x8m.4xlarge.1c
32-core 256 GB
0.3377
243.144
2958.252
pgro.x8m.8xlarge.1c
64-core 512 GB
0.6753
486.216
5915.628
-