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

  • Introduction

    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 that use the shared resource group for scheduling 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 Exclusive resource groups for scheduling.

  • Billing principle

    If your node is scheduled by hour or minute, multiple instances are generated for the node every day. If you use the shared resource group for scheduling to schedule the node, you are charged for the scheduling based on the number of instances that are generated for the node and successfully run. You can view the number of instances generated for nodes that are scheduled by using the shared resource group for scheduling in a workspace in Operation Center. To view the number of instances, perform the following operations: Go to Operation Center and choose Cycle Task Maintenance > Cycle Instance in the left-side navigation pane. On the Instance Perspective tab of the Cycle Instance page, select Common resource group from the Scheduling Resource Group drop-down list.

Billable item

The billable item of the shared resource group for scheduling is the instances generated for a node that is scheduled by using the resource group. You are charged for the instances that meet the following conditions:
  • The nodes for which instances are generated are committed to the scheduling system.

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

  • The 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 per day. If the number of instances generated per 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 granularity

Billable items are charged based on the Alibaba Cloud account to which the billable items belong and the region in which the billable items reside. The billable items in each region of each Alibaba Cloud account are independently charged.

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.
RegionBilling tierBilling cyclePrice

China (Hangzhou)

China (Shanghai)

China (Beijing)

China (Shenzhen)

China (Chengdu)

China (Zhangjiakou)

China (Hong Kong)

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

Singapore

Australia (Sydney)

Malaysia (Kuala Lumpur)

Indonesia (Jakarta)

Japan (Tokyo)

US (Silicon Valley)

US (Virginia)

Germany (Frankfurt)

UK (London)

UAE (Dubai)

India (Mumbai)

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

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, but instances that have been started can run 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.