Scheduling fees are generated when data synchronization tasks and data computing tasks are deployed to the production environment for scheduling. Data synchronization tasks include batch synchronization tasks and full and incremental synchronization tasks. Data computing tasks include PyODPS tasks and E-MapReduce (EMR) Hive tasks. DataWorks charges you based on the resource group type that you select. This topic describes the billing details of each type of resource group.
Fee generation scenarios
Scheduling fees are generated when you run data synchronization tasks or data computing tasks in Operation Center in different environments.
Scheduling fees are generated when auto triggered tasks, data backfill tasks, and test tasks are run in Operation Center in the production environment.
Scheduling fees are generated when data backfill tasks and test tasks are run in Operation Center in the development environment.
NoteAuto triggered tasks cannot be run in Operation Center in the development environment.
For more information about task types supported by DataWorks, see DataWorks nodes.
Fee measurement basis
When a task scheduled by hour or minute is run, multiple instances are generated for the task every day. You are charged for the number of instances that are generated and successfully run. You can go to the O&M Dashboard page in Operation Center to view the number of tasks in the current workspace and the resource usage of each resource group within a specified time period.
Billing
Scheduling fees vary based on the resource group type that you select.
If you did not activate DataWorks in any region, you can purchase and use only serverless resource groups after you activate DataWorks. For more information about how to activate DataWorks, see Activate DataWorks.
Serverless resource groups support more capabilities than old-version resource groups and can be purchased in a more unified manner. If you have purchased an old-version resource group, we recommend that you switch from the old-version resource group to a serverless resource group. For more information, see Comparison between serverless resource groups and old-version resource groups and Change from an old-version resource group to a serverless resource group.
Resource group type | Description | Billing details |
Serverless resource group (recommended) | This type of resource group is exclusively used by each tenant and is suitable for more scenarios. You can use one serverless resource group to complete operations such as data synchronization, task scheduling, and debugging and calling of DataService Studio APIs. You no longer need to separately purchase and configure resource groups for different scenarios. | A maximum of 200 instances can be concurrently run at a time. You are charged for the number of instances that are successfully run regardless of whether the subscription or pay-as-you-go billing method is used. For more information about task scheduling fees, see the Appendix: Billing of task scheduling section of the "Billing of serverless resource groups" topic. |
Old-version resource group |
|
|
References
For more information about the billing of serverless resource groups, see Billing of serverless resource groups.
For more information about how to create and use a serverless resource group, see Create and use a serverless resource group.
For more information about resource groups, see Overview.