Core billing scenarios

更新时间:
复制 MD 格式

This topic explains the costs of using different features in various scenarios.

Important

Data integration costs

Data integration and related operations may incur the following costs:

  • Costs billed by DataWorks (appear in your DataWorks bill)

    • Resource group fees: Data synchronization tasks run on resource groups. Depending on the resource group type, you will be charged for a serverless resource group or an exclusive resource group for Data Integration.

      If you use large model services for data processing during synchronization, this also incurs fees for a serverless resource group.
    • Task scheduling fees: If a synchronization task is deployed to the production environment for scheduled runs, you will be charged task scheduling fees (when using a serverless resource group) or fees for an exclusive resource group for scheduling (when using an exclusive resource group).

    • Data Quality fees: If you configure quality monitoring for a periodic task and an instance is successfully triggered, you are charged Data Quality instance fees.

    • Intelligent baseline fees: If you configure an intelligent baseline for a periodic task, you will be charged intelligent baseline instance fees for each enabled intelligent baseline.

    • Alert SMS and phone call fees: If you configure monitoring alerts for a synchronization task and an SMS or phone alert is triggered, you will be charged alert SMS and phone call fees.

      Note

      Modules involved: Data Integration, Data Studio, and Operation Center.

  • Related costs not billed by DataWorks (do not appear in your DataWorks bill)

    When you run Data Integration tasks, DataWorks does not bill for certain costs that result from your synchronization task configuration. Examples include database fees for data transfer, compute and storage fees for the underlying compute engine, network service fees (such as Express Connect, shared bandwidth, and EIPs), and fees for the large model services from Alibaba Cloud Model Studio or PAI for intelligent data processing.

    Note

    If you use an exclusive resource group for Data Integration, internet traffic fees are billed by DataWorks.

Data Studio costs

Data development and related operations may incur the following costs:

  • Costs billed by DataWorks (appear in your DataWorks bill)

    • Resource group fees: Node development and individual development environments use a resource group. Depending on the resource group type, you are charged for a serverless resource group or an exclusive resource group for scheduling.

      If you use large model services, you are also charged for a serverless resource group.
    • Task scheduling fees: If a task is deployed to the production environment for scheduled runs, you will be charged task scheduling fees (when using a serverless resource group) or fees for an exclusive resource group for scheduling (when using an exclusive resource group).

    • Data Quality fees: If you configure quality monitoring for a periodic task and an instance is successfully triggered, you are charged Data Quality instance fees.

    • Intelligent baseline fees: If you configure an intelligent baseline for a periodic task, you will be charged intelligent baseline instance fees for each enabled intelligent baseline.

    • Alert SMS and phone call fees: If you configure monitoring alerts for a periodic task and an SMS or phone alert is triggered, you will be charged alert SMS and phone call fees.

      Note

      Modules involved: Data Studio, Data Quality, and Operation Center.

  • Related costs not billed by DataWorks (do not appear in your DataWorks bill)

    When you run data development node tasks, related compute engine and storage fees, such as OSS storage fees, are not billed by DataWorks.

Data analysis costs

Using Data Analysis may incur the following costs:

  • Costs billed by DataWorks (appear in your DataWorks bill)

  • Related costs not billed by DataWorks (do not appear in your DataWorks bill)

    When you run Data Analysis tasks, related compute and storage fees for the compute engine are not billed by DataWorks.

Data service costs

The following costs may be incurred when you use Data Service:

  • Resource group fees: A resource group is required to generate API services from a data source and call them. Configuring CUs for Data Service in Quota Management incurs fees for a serverless resource group or an exclusive resource group for Data Service.

    Important

    Regardless of whether Data Service APIs are called, as long as a CU quota is configured, the CUs are considered occupied and will continuously incur fees.

    In the left-side navigation pane, click Resource Group to view its details page. Click Quota Management at the top of the page. In the Data Service row, you can view the Current Occupied CUs and the CU Limit. A hyphen (-) indicates that there is no upper limit.

  • Task scheduling fees: When you use Data Push, billable instances are calculated based on the number of push instances, incurring task scheduling fees.

FAQ

Q: How do I estimate or view the CU consumption for an SQL query task?

A: This depends on the compute engine you use.

  • For the MaxCompute engine: A pre-run cost estimation feature is available. Before running an SQL statement, click the Estimate Cost button to view the projected cost and manage your expenses.

    -- Read sample data
    --- Enable the three-layer model of MaxCompute
    SET odps.namespace.schema = true
    ;
    SELECT  user_id -- User ID (not a real ID), obtained from sampling & data masking.
            ,item_id -- Item ID (not a real ID), obtained from sampling & data masking.
            ,item_category -- Item category ID (not a real ID), obtained from sampling & data masking.
            ,behavior_type -- User behavior type, such as browse (pv), add to favorites (fav), add to cart (cart), or purchase (buy).
            ,behavior_time -- Behavior time, accurate to the hour.
    FROM    bigdata_public_dataset.commerce.commerce_taobao_shopping
    LIMIT   100
    ;
  • For other compute engines (such as Hologres and EMR): DataWorks does not currently support pre-run cost estimation.

Q: How do I estimate or view the CU consumption for a node task?

A: Cost estimation is supported only for MaxCompute SQL tasks. For other node types, you can only estimate the CU consumption. The actual runtime varies based on task complexity.