All Products
Search
Document Center

DataWorks:Serverless resource group: More task types will be switched from compute to scheduling (2)

Last Updated:Jun 15, 2026

Dear DataWorks users,

To better meet your task scheduling needs and improve scheduling resource utilization, DataWorks will switch SQL nodes for certain database types from compute tasks to scheduling tasks.

Important
  • After SQL nodes are switched to scheduling tasks, only scheduling fees are charged. Compute fees are no longer charged, which significantly reduces your costs.

  • The switch is seamless and does not affect any running task nodes.

The database types of the SQL nodes added in this switch are: ClickHouse, ADB for MySQL, ADB for PostgreSQL, Hologres SQL, and Serverless StarRocks SQL.

The switch will take place from June 15, 2026 to June 30, 2026 (UTC+8). After the switch is complete, compute fees will no longer be charged for the preceding node types across all regions, and only scheduling instance fees will be charged.

From now until June 30, 2026, regions that have already been switched will also no longer be charged compute fees, and only scheduling instance fees will be charged.

Note

When you use a data source or compute resource to run SQL statements, the compute engine fees are charged by the corresponding engine product. These fees are reflected in the bills of the respective engine products (such as MaxCompute and Hologres) and are not included in DataWorks platform service fees. For more information, see Billing overview.

Tips

After the switch to scheduling nodes, we recommend that you adjust the scheduling concurrency configuration based on your task volume. If you have a large number of SQL node tasks, increase the scheduling concurrency for a better scheduling experience. The specific rules are as follows:

  • Pay-as-you-go resource groups:

    • The default scheduling concurrency is 50.

    • The maximum value can be adjusted to 200.

    • If this still does not meet your requirements, we recommend that you switch to a subscription resource group.

  • Subscription resource groups:

    • The default scheduling concurrency is 50.

    • Submit a ticket to contact technical support for adjustment. The maximum value can be adjusted to 200 + (CU - 50) × 4, with an upper limit of 500.

If you have any questions about scheduling concurrency adjustments or billing changes, submit a ticket to contact technical support.

Thank you for your support and understanding of DataWorks.