DataWorks provides shared resource groups for scheduling for you to schedule nodes. Shared resource groups for scheduling are billed in pay-as-you-go mode. This topic describes the billing details of shared resource groups for scheduling.

Background information

Shared resource groups for scheduling are shared resources provided by DataWorks and are billed in pay-as-you-go mode. Shared resource groups for scheduling are used by all DataWorks tenants. During peak hours, this may lead to the situation that tenants preempt resources. In this case, nodes may not be run as scheduled.

To make sure that your nodes run as scheduled, you can purchase a resource plan of shared resource groups for scheduling or use exclusive resource groups for scheduling. For more information about shared resource groups and resource plans, see Shared resource groups and resource plans for shared resource groups. For more information about exclusive resource groups for scheduling, see Exclusive resource groups for scheduling.

Billable items

Bills are generated based on node instances that run on shared resource groups for scheduling. You are charged for 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 node instances, manually triggered node instances, test instances, and data backfill node instances.

  • The node instances have been run.

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

Note
  • When a node runs on an exclusive resource group for scheduling, you are charged only for the exclusive resource group for scheduling that you use, not the shared resource group for scheduling. For more information, see Exclusive resource groups for scheduling.
  • If the number of instances per day exceeds 120,000, the excess instances cannot be scheduled. If the number of instances that are required for your business exceeds the upper limit,submit a ticket to seek technical help from Alibaba Cloud.

Billing cycles and prices

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

China (Hangzhou)

China (Shanghai)

China (Beijing)

China (Shenzhen)

China (Chengdu)

China (Zhangjiakou)

China (Hong Kong)

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

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 USD 0.00/day
11 to 500 successful instances/day Daily USD 0.23/day
501 to 5,000 successful instances/day Daily USD 13.93/day
5,001 to 20,000 successful instances/day Daily USD 34.82/day
20,001 to 50,000 successful instances/day Daily USD 62.68/day
50,001 to 120,000 successful instances/day Daily USD 139.30/day

Deduction

At 00:00 every day, the billing system starts to calculate the number of instances that were run on the previous calendar day and deducts a fee based on only one of the pricing tiers that are specified in the preceding billing standards. No additional fee is deducted.

For example, you deploy a DataWorks workspace in the China (Shanghai) region and run 502 instances on April 30, 2019. The billing system deducts a fee of USD 9.26 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 you receive a notification, you must top up your Alibaba Cloud account as soon as possible.
  • If your bill is overdue for more than 360 hours, the service is suspended. At this time, instances that have not been run cannot be started, but instances that have been started can run until they are finished.
  • If you top up your 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.