The shared resource group for Data Integration is a type of shared resource group provided by DataWorks. The shared resource group for Data Integration is used only for debugging and is charged based on the pay-as-you-go billing method. This topic describes the billing details of the shared resource group for Data Integration.
Background information
Resources in the shared resource group for Data Integration are shared by all DataWorks tenants. During peak hours, tenants may compete for resources. In this case, nodes may not be scheduled and run in time.
To ensure that your nodes can be normally scheduled and run, you can purchase exclusive resource groups for Data Integration. For more information, see Exclusive resource groups for Data Integration.
Billable items
- Data Integration node instances use resources in both the shared resource group for Data Integration and the shared resource group for scheduling. Both the shared resource group for Data Integration and the shared resource group for scheduling are charged based on the pay-as-you-go billing method.
- Nodes that are run on exclusive resource groups for Data Integration are not counted in the number of nodes that are run on the shared resource group for Data Integration. For information about the billing of an exclusive resource group for Data Integration, see Billing of exclusive resource groups for Data Integration (subscription).
Billing granularity
Billable items are charged based on the Alibaba Cloud account to which the billable items belong and the region in which the billable items reside. The billable items in each region of each Alibaba Cloud account are independently charged.
Billing cycles and prices
Region | Billing tier | Billing cycle | Price |
---|---|---|---|
China (Hangzhou) China (Shanghai) China (Beijing) China (Shenzhen) China (Chengdu) China (Zhangjiakou) China (Hong Kong) | 1 to 10 successful instances/day | Daily | USD 0.00/day |
11 to 500 successful instances/day | Daily | USD 0.15/day | |
501 to 5,000 successful instances/day | Daily | USD 0.93/day | |
5,001 to 20,000 successful instances/day | Daily | USD 3.10/day | |
20,001 to 50,000 successful instances/day | Daily | USD 7.74/day | |
50,001 to 120,000 successful instances/day | Daily | USD 15.48/day | |
Singapore Australia (Sydney) Malaysia (Kuala Lumpur) Indonesia (Jakarta) Japan (Tokyo) US (Silicon Valley) US (Virginia) Germany (Frankfurt) UK (London) UAE (Dubai) | 1 to 10 successful instances/day | Daily | USD 0.00/day |
11 to 500 successful instances/day | Daily | USD 0.23/day | |
501 to 5,000 successful instances/day | Daily | USD 1.39/day | |
5,001 to 20,000 successful instances/day | Daily | USD 4.64/day | |
20,001 to 50,000 successful instances/day | Daily | USD 11.61/day | |
50,001 to 120,000 successful instances/day | Daily | USD 23.22/day |
Deduction
At 00:00 every day, the billing system starts to calculate the number of instances that were successfully run on the previous calendar day and deducts the fee based only on the related billing tier that is described in the preceding table. No additional fee is deducted.
For example, you configure two data synchronization nodes Node A and Node B in your DataWorks workspace that resides in the China (Shanghai) region and use shared resources to run the nodes. If you set the number of parallel threads for Node A to 2 and schedule Node A by day, the system generates one instance every day. If you set the number of parallel threads for Node B to 5 and schedule Node B by hour, the system generates 24 instances every day.
- The total number of parallel threads that are used per day is 122. The number is calculated based on the following formula:
Number of parallel threads × Number of instances generated per day
. In this example, two nodes are configured. Therefore, the total number of parallel threads is the sum of the number of parallel threads for Node A and that for Node B. - The total number of parallel threads per day is 122, which falls within the range of 11 to 500. You are charged a daily fee of USD 0.15 based on the price that corresponds to this range.
Overdue payments
- If your bill is overdue for more than 360 hours, the service is suspended. As a result, instances that have not been run cannot be started. However, running instances can be retained until they are finished.
- If you top up your Alibaba Cloud account within 360 hours after your bill becomes overdue, the service is not suspended.
FAQ
For information about FAQ about the shared resource group for Data Integration, see Shared resource group for Data Integration (debugging).