Serverless resource group billing

Billing scenarios

Fees for a DataWorks serverless resource group include a resource usage fee and a task scheduling fee.

• Resource usage fee: Certain DataWorks tasks consume compute units (CUs) from a serverless resource group during execution. Fees are calculated based on total CU consumption. This portion of the fee is the resource usage fee, measured in CUs.

  Where, 1 CU = 1 CPU core + 4 GiB of memory.

• Task scheduling fee: A task scheduling fee applies when you publish a task for periodic scheduling in the production environment. These tasks incur only the task scheduling fee, not a resource usage fee. The fee is calculated based on the number of successful instance runs, excluding dry runs.

  A serverless resource group supports a maximum of 200 concurrent instances. This limit matches or exceeds the concurrency of all legacy resource group types. You do not need to consider the CU specifications for the serverless resource group.

Notes

• With pay-as-you-go serverless resource groups, resource contention may occur during peak hours, and resource availability timeliness cannot be fully guaranteed.

• You can upgrade a pay-as-you-go resource group to a subscription resource group, but a subscription resource group cannot be converted to a pay-as-you-go resource group.

• When new users activate DataWorks, a pay-as-you-go serverless resource group is purchased by default. No fees are incurred if you do not use it. For billing details, see Billing details.

• The total available CUs for a subscription serverless resource group is the CU amount specified at the time of purchase. Actual usage does not exceed this limit. To obtain more CUs, you must perform a scale-up operation.

• When all CUs of a subscription serverless resource group are occupied, newly submitted tasks enter a queue and wait until idle CUs are released before execution begins.

Performance metrics

Serverless resource groups are billed based on CU consumption, where 1 CU = 1 CPU core + 4 GiB of memory. When using a serverless resource group, plan the resource group specifications based on your development scenarios and task types.

Billing models

Serverless resource groups are available in two billing models: subscription (monthly or yearly) and pay-as-you-go.

• Serverless resource group (subscription): You estimate the required CU amount and usage duration in advance and pay accordingly. In addition to the subscription fee, no other resource usage fees are charged by DataWorks for data synchronization, data computing, or debugging/calling Data Service APIs.

• Serverless resource group (pay-as-you-go): You use the product features first and then pay based on your total CU consumption. Running certain tasks (such as batch synchronization tasks, Data Service tasks, and data development tasks) on a pay-as-you-go serverless resource group incurs corresponding resource usage fees.

The following table compares the two billing models:

Billing standards

View bill details

When you view bill details in the Billing Management console, the billing item and billing code for a serverless resource group are as follows:

• Pay-as-you-go: The billing item is Serverless Resource Group CU-Hours (Pay-As-You-Go), and the billing code is exresource_cu_hour_post.

• Subscription: The billing item is General-purpose exclusive resource group subscription (hybrid billing), and the billing code is cu_number.

For more information, see Purchase a serverless resource group.

Expiration and renewal

If a subscription serverless resource group is about to expire, you can renew it. If you do not renew the resource group, it will be suspended or released. For more information about renewal, see Renew a serverless resource group.

Scaling fees

Subscription serverless resource groups support scaling up or down after purchase based on your actual needs. Scaling involves fee changes. For information about the fee calculation logic before and after scaling, see Scaling fees for serverless resource groups.

Next step

You can purchase a resource group and use it for tasks such as data integration, data development, and data services. For information about how to purchase a resource group, bind it to a workspace, and connect the resource group to your network, see Purchase and use a serverless resource group.

Additional information

Appendix 2: Billing modes for task execution

When you run a node task in DataWorks, the compute fee is not necessarily charged by DataWorks. You need to identify which compute engine or resource actually executes the task. The following three scenarios exist:

Note

A task scheduling fee is incurred for all tasks published to the production environment for periodic scheduling.

Execution method	Representative task nodes	Compute resource provider	Cost breakdown
Method 1: Compute tasks are submitted to and executed on a serverless resource group	PyODPS, Shell, Data Integration, Data Quality	Serverless resource group	Serverless resource group fee only
Method 2: Compute tasks are submitted through a serverless resource group to a third-party engine for execution	EMR Hive, Hologres SQL	Serverless resource group + third-party engine	Serverless resource group fee + third-party engine fee
Method 3: Scheduling tasks are submitted through the scheduling center to a third-party engine for execution	MaxCompute SQL, Flink SQL	Third-party engine	Third-party engine fee