This topic describes the billable items and billing methods of Elastic Algorithm Service (EAS).
Billable items
The following figure shows the billable items of EAS.
Billing methods
The following table describes the billing methods for public resource groups and dedicated resource groups.
Billable resource | Billable item | Billing rule | Billing method | How to stop billing |
Public resource group | The service time of the model service | Bills are generated based on how long the model service occupies public resources. Billing starts immediately after model services are created. | Pay-as-you-go | Stop the model service. |
Dedicated resource group | The service time of the model service | You are charged only for nodes in dedicated resource groups. No additional fees are charged when you deploy model services in dedicated resource groups. For pay-as-you-go nodes, billing starts immediately the moment when nodes are created in dedicated resource groups. | Pay-as-you-go | Delete the pay-as-you-go resource group node. |
Subscription | N/A. | |||
System disk | The capacity and service time of the system disk | Billing starts immediately after the system disk is created. | Pay-as-you-go |
|
The capacity and service time of the system disk | Billing starts immediately after the system disk is created. | Subscription | N/A. |
Public resource group
The public resource group provides two options to obtain EAS nodes: resource-based configuration and instance type configuration. The following table describes the billing of each option.
Option | Calculation formula | Unit price | Usage duration | Scaling | Usage notes |
Resource-based configuration |
| Fees are calculated per minute on a pay-as-you-go basis, rounded down to the minute. For more information about the hourly prices of vCPU and memory resources, see Resource-based configuration. |
| Scale-out: EAS generates fees for new resources. Scale-in: EAS stops charging for resources that are released. |
|
Instance type configuration |
| Fees are calculated per minute on a pay-as-you-go basis and rounded down to the minute. The pricing of resources varies based on the region and the instance type. For more information about the hourly prices of the supported instance types, see Appendix: Pricing of specific instance types for public resource groups. |
| N/A. |
|
Item | Price |
CPU | USD 0.03 per vCPU-hour |
Memory | USD 0.004 per GB-hour |
Dedicated resource group
Dedicated resource groups provide subscription and pay-as-you-go resources. The following table describes the billing of each mode.
Billing mode | Calculation formula | Unit price | Usage duration | Scaling | Usage notes |
Subscription |
| For more information about the pricing of subscription resources in dedicated resource groups, go to the EAS pre-payment for dedicated machine page. |
| N/A. |
|
Pay-as-you-go |
| For more information about the pricing of pay-as-you-go resources in dedicated resource groups, go to the EAS post-payment for dedicated machine page. |
| Scale-out: EAS generates fees for new resources. Scale-in: EAS stops charging for resources that are released. |
|
System disk
System disks support the subscription and pay-as-you-go billing methods. The following table describes the billing of each mode.
Billing mode | Calculation formula | Unit price | Usage duration | Scaling | Usage notes |
Subscription |
| For more information about the pricing in different regions, see the Subscription pricing section in this topic. |
| N/A. | N/A. |
Pay-as-you-go |
| For more information about the pricing in different regions, see the Pay-as-you-go pricing section in this topic. |
| N/A. | N/A. |
Region | Price (USD per GB-month) |
India (Mumbai) | 0.214 |
Singapore | 0.224 |
Indonesia (Jakarta) | 0.214 |
China (Beijing) | 0.153 |
China (Hangzhou) | 0.153 |
China (Hong Kong) | 0.224 |
China (Shanghai) | 0.153 |
China (Shenzhen) | 0.153 |
China (Zhangjiakou) | 0.153 |
Germany (Frankfurt) | 0.24 |
US (Virginia) | 0.224 |
US (Silicon Valley) | 0.224 |
Region | Price (USD per GB-month) |
India (Mumbai) | 0.0005 |
Singapore | 0.0005 |
Indonesia (Jakarta) | 0.0005 |
China (Beijing) | 0.00032 |
China (Hangzhou) | 0.00032 |
China (Hong Kong) | 0.0005 |
China (Shanghai) | 0.00032 |
China (Shenzhen) | 0.00032 |
China (Zhangjiakou) | 0.00032 |
Germany (Frankfurt) | 0.0006 |
US (Virginia) | 0.0005 |
US (Silicon Valley) | 0.0005 |
Billing examples
The following examples are for reference only. The actual prices listed on the EAS buy page of the Platform for AI (PAI) console shall prevail.
Public resource group
Example:
You deploy a model service in the China (Hangzhou) region. The service is deployed by using the resource-based configuration in the public resource group.
The model service occupies 2 vCPU cores and 8 GB of memory and starts to run at 09:00:00 (UTC+8) on June 3, 2019.
You reduce the resources that are occupied by the model service to 1 vCPU core and 4 GB of memory at 10:00:00 (UTC+8) on June 3, 2019.
You increase the resources that are occupied by the model service to 4 vCPU cores and 16 GB of memory at 11:00:00 (UTC+8) on June 3, 2019.
The model service stops running at 12:00:00 (UTC+8) on June 3, 2019.
Cost calculation:
Bill amount = 2 × 0.03 + 8 × 0.004 + 1 × 0.03 + 4 × 0.004 + 4 × 0.03 + 16 × 0.004 = USD 0.322
Dedicated resource group
Subscription
Example:
You created two 3-month subscription T4 GPU instances (4 vCPU cores, 15 GB) in the China (Hangzhou) region. Each instance costs USD 570 per month.
Cost calculation:
Bill amount = 2 × 570 × 3 = USD 3,420
Pay-as-you-go
Example:
You purchase two pay-as-you-go Elastic Compute Service (ECS) instances whose instance type is ecs.g6.6xlarge in the China (Hangzhou) region, and use the instances for 45 minutes. Each ECS instance has 24 vCPU cores and 96 GB of memory, and the unit price is USD 2.94 per hour. This unit price is only for reference. The prices listed in the ECS console shall prevail.
Cost calculation:
Bill amount = 2 × (2.94/60) × 45 = USD 4.41
System disk
Subscription
Example:
You deployed two subscription nodes to a dedicated resource group in the China (Hangzhou) region for three months. Each node provides 300 GB of system disk capacity.
Cost calculation:
Bill amount = 2 × (300 - 200) × 0.153 × 3 = USD 91.8
Pay-as-you-go (applicable to dedicated resource groups)
Example:
You deployed two pay-as-you-go nodes to a dedicated resource group in the China (Hangzhou) region and used the nodes for 5 hours. Each node provides 300 GB of system disk capacity.
Cost calculation:
Bill amount = 2 × (300 - 200) × 0.00032 × 5 = USD 0.32
Pay-as-you-go (applicable to the public resource group)
Example:
You deploy two pay-as-you-go nodes to the public resource group in the China (Hangzhou) region and use the nodes for 5 hours. The size of each node provides 300 GB system disk capacity.
Cost calculation:
Bill amount = 2 × (300 - 30) × 0.00032 × 5 = USD 0.864
Overdue payments
Causes
Your account balance is insufficient to pay your overdue payment.
Subscription nodes: Your account balance is insufficient to complete renewal orders.
Pay-as-you-go nodes: Your account balance is insufficient to settle the bill of the previous billing cycle. If the payment fails, your account has an overdue payment.
Service suspension
Subscription nodes
If a node expires or fails to be renewed, the node is released. After the node is released, the node stops providing services and the EAS services that use this node enter the waiting state.
If you renew the node within 15 calendar days (360 hours) after the node expires, the node is restored.
Otherwise, the node is permanently deleted.
Pay-as-you-go resource groups (including public resource groups and pay-as-you-go nodes in resource groups)
If you settle the overdue payments within 24 hours after the payments become overdue, your resource groups remain available. Otherwise, public resource groups are stopped and pay-as-you-go nodes are released. After the nodes are released, the nodes enter the stopped state and the EAS services that use these nodes enter the waiting state.
If you settle the overdue payments within 15 calendar days (360 hours) after the payments become overdue, the system recovers the resource groups and the data in the groups is retained. Otherwise, the stopped nodes are permanently deleted.
View overdue payments
Log on to the Expenses and Costs console.
On the Account Overview page, view the overdue payments.
Renewal
Subscription nodes in dedicated resource groups can be automatically renewed upon expiration or manually renewed.
Auto-renewal
If you do not want to manually renew a subscription node, you can select Auto-renewal when you purchase the node. For more information, see Work with dedicated resource groups.
Manual renewal
To manually renew a subscription node, go to the details page of the dedicated resource group to which the node belongs, find the node that you want to renew, and then click Work with dedicated resource groups.
in the Actions column. For more information, see
Refund policy
Fees incurred in pay-as-you-go mode cannot be refunded.