DataWorks provides the shared resource group for scheduling for you to schedule nodes. The shared resource group for scheduling is charged based on the pay-as-you-go billing method. This topic describes the billing details of the shared resource group for scheduling.

Background information

The shared resource group for scheduling is a type of shared resource group provided by DataWorks and is charged based on the pay-as-you-go billing method. Resources in the shared resource group for scheduling are shared by all DataWorks tenants. During peak hours, tenants may compete for resources. In this case, nodes may not be scheduled and run in time. To ensure that your nodes can be normally scheduled and run, you can use exclusive resource groups for scheduling. For more information about an exclusive resource group for scheduling, see Overview.

Billable items

Bills are generated based on the node instances that are run on the shared resource group for scheduling. You are charged for the node instances that meet the following conditions:
  • The node instances are committed to the scheduling system.

    After nodes are committed to the scheduling system, you are charged for all the generated instances, except those generated by zero load nodes. The instances include auto triggered instances, manually triggered instances, test instances, and data backfill instances.

  • The node instances are successfully run.

    You are charged only for instances that are successfully run in Operation Center. You are not charged for instances that are generated but not run, instances that are frozen, or dry-run instances.

Note
  • When a node is run on an exclusive resource group for scheduling, you are charged only for the exclusive resource group for scheduling that you use, and not for the shared resource group for scheduling. For more information, see Billing and related operations.
  • Only 120,000 instances can be scheduled to run every day. If the number of instances generated every day exceeds 120,000, the excess instances cannot be scheduled. If the number of instances generated in your business exceeds the upper limit,submit a ticket to contact the technical personnel.

Billing cycles and prices

You are charged daily based on a six-tier pricing schedule and the total number of instances that are successfully run per day. The following table describes the billing standards.
Region Billing tier Billing cycle Price (USD/day)

China (Hangzhou)

China (Shanghai)

China (Beijing)

China (Shenzhen)

China (Chengdu)

China (Zhangjiakou)

China (Hong Kong)

1 to 10 successful instances/day Daily 0.00
11 to 500 successful instances/day Daily 0.15
501 to 5,000 successful instances/day Daily 9.29
5,001 to 20,000 successful instances/day Daily 23.22
20,001 to 50,000 successful instances/day Daily 41.79
50,001 to 120,000 successful instances/day Daily 92.87

Singapore (Singapore)

Australia (Sydney)

Malaysia (Kuala Lumpur)

Indonesia (Jakarta)

Japan (Tokyo)

US (Silicon Valley)

US (Virginia)

Germany (Frankfurt)

UK (London)

UAE (Dubai)

1 to 10 successful instances/day Daily 0.00
11 to 500 successful instances/day Daily 0.23
501 to 5,000 successful instances/day Daily 13.93
5,001 to 20,000 successful instances/day Daily 34.82
20,001 to 50,000 successful instances/day Daily 62.68
50,001 to 120,000 successful instances/day Daily 139.30

Deduction

At 00:00 every day, the billing system starts to calculate the number of instances that were successfully run on the previous calendar day and deducts the fee based only on the related billing tier that is described in the preceding table. No additional fee is deducted.

For example, 502 instances in a DataWorks workspace that resides in the China (Shanghai) region are successfully run on April 30, 2019. The billing system deducts a fee of USD 9.29 after 00:00 on May 1, 2019.

Overdue payments

If your Alibaba Cloud account has an overdue payment, you are given a 360-hour grace period and the billing system sends you notifications at the 192nd, 288th, and 336th hours after your bill becomes overdue. After you receive a notification, you must top up your account at the earliest opportunity.
  • If your bill is overdue for more than 360 hours, the service is suspended. As a result, instances that have not been run cannot be started. However, running instances can be retained until they are finished.
  • If you top up your Alibaba Cloud account within 360 hours after your bill becomes overdue, the service is not suspended.
  • If your bill becomes overdue again after settlement, you are given another 360-hour grace period before the service is suspended.