DataWorks charges scheduling instance fees when you run scheduling tasks, such as data integration and data computing, using a Serverless resource group or a shared resource group for scheduling. The fees are based on the number of instances that run successfully each day.
Comparison of resource group types
Both Serverless resource groups and shared resource groups for scheduling provide scheduling capabilities. They use the same tiered pricing model based on the number of successful instances.
This topic focuses only on the scheduling instance fees generated by task scheduling. Serverless resource groups have separate subscription and pay-as-you-go billing methods. For more information, see Serverless resource group billing.
Resource group type | Introduction to resource groups | Billing method |
Serverless resource group (Recommended) | Each tenant has exclusive use of the resource group. This provides good resource isolation and stable performance. | Tiered pricing based on the number of successful instances. This is the billing method described in this topic. |
shared resource group for scheduling | Resources are shared among all tenants and are applicable only to scheduling tasks. Resource contention may occur during peak hours. This can prevent tasks from running on time. There is also a limit on the number of instances. |
Billing scenarios
Scheduling fees are charged when you use supported development nodes in DataWorks to run data integration tasks in scheduling tasks or compute-optimized tasks in the following scenarios:
In the production environment of the Operation Center: running auto triggered tasks, data backfill tasks, and test tasks.
In the developer environment of the Operation Center: running data backfill tasks and test tasks.
The Operation Center in the developer environment does not support auto triggered tasks.
Billing metrics
Scheduling instance fees are calculated based on task instances. DataWorks bills for an instance only if it meets both of the following conditions:
Submitted to the scheduling system: All instances generated by nodes submitted to the scheduling system are billable, except for instances generated by zero load nodes. This includes recurring, one-time, test, and data backfill instances.
Successfully run: Only instances that run successfully in the Operation Center are billed. Instances that are generated but have not run, fail to run, are frozen, or are dry-runs are not billed. A dry-run is an instance that the platform marks as successful without executing the task.
Example: An hourly task is scheduled to run once every hour from 00:00 to 23:59 each day. This generates 24 instances daily. If all 24 instances run successfully, the billable instance count is 24.
Pricing
The shared resource group for scheduling has usage limits. If the daily number of instances reaches or exceeds 120,000, you may reach the upper instance limit, which can prevent instances from running properly. For high-volume workloads, use a Serverless resource group to avoid this limitation.
DataWorks uses a 12-tiered pricing model for scheduling instance fees. The fees are based on the number of successful instances per day. The daily fee is determined by the pricing tier that corresponds to the total number of successful instances for that day.
Billing cycle: Daily.
Billing granularity: Number of successful instances per day.
Free quota: DataWorks provides a free quota of 10 successful instances per day.
Pricing details:
Region
Billing tier
Pricing
China (Hangzhou)
China (Shanghai)
China (Beijing)
China (Shenzhen)
China (Chengdu)
China (Hong Kong)
1–10 successful instances/day
Free
11–500 successful instances/day
0.15 USD
501–5,000 successful instances/day
9.29 USD
5,001–20,000 successful instances/day
23.22 USD
20,001–50,000 successful instances/day
41.79 USD
50,001–120,000 successful instances/day
92.87 USD
120,001–300,000 successful instances/day
204.31USD
300,001–700,000 successful instances/day
464.33USD
700,001–1,500,000 successful instances/day
975.10USD
1,500,001–3,200,000 successful instances/day
2,074.02USD
3,200,001–7,000,000 successful instances/day
4,333.78USD
7,000,001–14,000,000 successful instances/day
8,590.17USD
Singapore
Malaysia (Kuala Lumpur)
Indonesia (Jakarta)
Japan (Tokyo)
US (Silicon Valley)
US (Virginia)
Germany (Frankfurt)
UK (London)
UAE (Dubai)
Thailand (Bangkok)
1–10 successful instances/day
Free
11–500 successful instances/day
0.23 USD
501–5,000 successful instances/day
13.93 USD
5,001–20,000 successful instances/day
34.82 USD
20,001–50,000 successful instances/day
62.68 USD
50,001–120,000 successful instances/day
139.30 USD
120,001–300,000 successful instances/day
306.46USD
300,001–700,000 successful instances/day
696.50USD
700,001–1,500,000 successful instances/day
1,462.65USD
1,500,001–3,200,000 successful instances/day
3,111.03USD
3,200,001–7,000,000 successful instances/day
6,500.67USD
7,000,001–14,000,000 successful instances/day
12,885.25USD
View bill details
When you view your bill details in Expenses and Costs, the Billing Item is Number of scheduled instances (Pay-As-You-Go) and the Billing Item Code is dide_create_public_alisa_post. For more information, see View billing details.
FAQ
Q: How do I calculate the cost of a single instance?
A: Scheduling instance fees use a tiered pricing model. A fixed daily fee is charged based on the tier that corresponds to the total number of successful instances for the day. Therefore, the cost of a single instance cannot be calculated, and bills cannot be queried for individual instances.
Q: How can I estimate the number of scheduling instances?
A: You can go to the Operation Center to view the total number of scheduled instances across the recurring instance, data backfill instance, test instance, and one-time instance lists.