After you activate Data Lake Analytics (DLA), you can select a billing method based on your requirements. DLA uses the pay-as-you-go billing method, which charges you based on the number of bytes scanned or based on the number of compute units (CUs) used.

  • Based on the number of bytes scanned

    By default, DLA charges you based on the number of bytes scanned. This billing method is suitable for scenarios in which data is not frequently queried and the amount of data queried is small. You are charged based on the scanned bytes. If no data queries occur, you are not charged. For more information, see Billing based on the volume of scanned data.

  • Based on the number of CUs used

    This billing method is suitable for scenarios in which data is frequently queried and the amount of data queried is large. It also helps you determine the costs of using DLA.

    If you use the billing method based on the number of CUs used, you can set MIN and MAX for the number of CUs required. MIN specifies the long-term required quota. This quota can be charged by using the subscription or pay-as-you-go billing method. If the quota is exceeded, the excess amount of CUs is charged on a pay-as-you-go basis. MAX specifies the maximum number of CUs that you can purchase. To achieve cost-effectiveness, you can set MIN to a small value and MAX to a value within a reasonable range. This way, you only pay for the quota specified by MIN and the CUs you actually use but still can use extra resources during peak hours. For more information, see Billing based on the number of CUs.

The following table describes the differences between the billing method based on the number of bytes scanned and the billing method based on the number of CUs used.
Based on the number of bytes scanned Based on the number of CUs used
Billing method You are charged based on the number of bytes scanned. Less queries incur less fees. This billing method is suitable for scenarios in which data is not frequently queried. You are charged based on the number of CUs that you purchase. Fees are not related to the amount of data scanned. This billing method is suitable for scenarios in which data is frequently queried.
Supported data sources OSS, Tablestore, ApsaraDB RDS for MySQL, ApsaraDB RDS for SQL Server, AnalyticDB for PostgreSQL, AnalyticDB for MySQL, MaxCompute, ApsaraDB for MongoDB, ApsaraDB for Redis, and Elasticsearch User-created HDFS, Oracle, Kudu, and Druid data sources in addition to all the data sources that the billing method based on the number of bytes scanned supports
Number of SQL statements that can be concurrently executed 10 100
Maximum SQL runtime 30 minutes 12 hours
Access to self-managed Hive Metastore Not supported Supported later (under development)
Built-in cache Not supported Supported later (under development)
UDF Not supported Supported later (under development)