Task scheduling fees are generated when data integration tasks, such as offline sync tasks and sync solution tasks, and data compute tasks, such as PyODPS and EMR Hive tasks, are published to the production environment and run on a Serverless resource group.
This topic describes the billing for task scheduling on Serverless resource groups only. For billing information about legacy resource groups, see Billing for exclusive resource groups for scheduling and Billing for shared resource groups for scheduling.
Billing scenarios
Scheduling fees are generated when supported developer nodes in DataWorks run data integration tasks in scheduling tasks or compute-optimized tasks in the following scenarios:
In the Operation Center for the production environment: running periodic timed scheduling tasks, data backfill tasks, and test tasks.
In the Operation Center for the development environment: running data backfill tasks and test tasks.
The Operation Center for the development environment does not support automatic periodic scheduling tasks.
Billing statistics
For hourly and minutely tasks, multiple instances are generated daily. Billing is based on the number of instances that are successfully run. Dry-run instances are not charged. A dry-run instance is one that the platform immediately marks as successful without actually running the task. You can go to the Operation Center dashboard to view the number of tasks in your workspace and the resource usage of each resource group for a specific time period.
Example of daily instance count: If a task is scheduled to run once every hour from 00:00 to 23:59, 24 instances are generated each day.
Billing standards and pricing
DataWorks uses a 12-tier pricing model for scheduling fees based on the number of successful instances per day. The daily fee is determined by the price tier that corresponds to your total number of successful instances on that day.
Billing cycle: Daily.
Billing granularity: Successful instances/day.
Free quota: DataWorks provides a daily free quota of 10 successful instances.
Pricing details:
Region
Billing tier
Price
China (Hangzhou)
China (Shanghai)
China (Beijing)
China (Shenzhen)
China (Chengdu)
China (Hong Kong)
1 to 10 successful instances/day
Free
11 to 500 successful instances/day
0.15 USD
501 to 5,000 successful instances/day
9.29 USD
5,001 to 20,000 successful instances/day
23.22 USD
20,001 to 50,000 successful instances/day
41.79 USD
50,001 to 120,000 successful instances/day
92.87 USD
120,001 to 300,000 successful instances/day
204.31 USD
300,001 to 700,000 successful instances/day
464.33 USD
700,001 to 1,500,000 successful instances/day
975.10 USD
1,500,001 to 3,200,000 successful instances/day
2074.02 USD
3,200,001 to 7,000,000 successful instances/day
4333.78 USD
7,000,001 to 14,000,000 successful instances/day
8590.17 USD
Singapore
Malaysia (Kuala Lumpur)
Indonesia (Jakarta)
Japan (Tokyo)
US (Silicon Valley)
US (Virginia)
Germany (Frankfurt)
UK (London)
UAE (Dubai)
Thailand (Bangkok)
1 to 10 successful instances/day
Free
11 to 500 successful instances/day
0.23 USD
501 to 5,000 successful instances/day
13.93 USD
5,001 to 20,000 successful instances/day
34.82 USD
20,001 to 50,000 successful instances/day
62.68 USD
50,001 to 120,000 successful instances/day
139.30 USD
120,001 to 300,000 successful instances/day
306.46 USD
300,001 to 700,000 successful instances/day
696.50 USD
700,001 to 1,500,000 successful instances/day
1462.65 USD
1,500,001 to 3,200,000 successful instances/day
3111.03 USD
3,200,001 to 7,000,000 successful instances/day
6500.67 USD
7,000,001 to 14,000,000 successful instances/day
12885.25 USD
View bill details
Task scheduling fees have a separate billing code from the billing code for Serverless resource groups. When you view bill details in Expenses and Costs, the Billable Item is Shared resource group for scheduling (Pay-As-You-Go) and the Billing Code is dide_create_public_alisa_post. For more information, see View bill details.
Appendix: Comparison of different resource groups
Task scheduling performance varies depending on the resource group type. For optimal performance, you can use a Serverless resource group. You can upgrade legacy resource groups.
Resource group type | Introduction to Resource Groups |
Serverless resource group (Recommended) | Each tenant has exclusive use of the resource group. It supports a wide range of applications. A single resource group can handle data integration, task scheduling, and DataService Studio API debugging and execution. You do not need to purchase and configure separate resource groups for each scenario. |
Exclusive resource group for scheduling | Exclusive to each tenant and applicable only to scheduling tasks. |
Shared resource group for scheduling | Shared by all tenants and applicable only to scheduling tasks. During peak hours, resource contention may occur among users, which can prevent tasks from being scheduled and run on time. |