This topic describes how to select a cost-effective billing method.
- Subscription: Computing resources are charged on a monthly or annual basis. Storage and download resources are charged on a pay-as-you-go basis.
- Pay-as-you-go: Storage, computing, and download resources are all charged on a pay-as-you-go basis.
For more information, see Overview. You can select a billing method with the help of Total Cost of Ownership (TCO) tools and the best practices of cost estimation.
- MaxCompute price calculator: This tool is suitable for the subscription billing method. To calculate the monthly cost, enter the required computing resources and the volumes of the data you want to upload and download.
- CostSQL: This tool is suitable for the pay-as-you-go billing method.
- You can run the cost sql command to estimate the cost of an SQL job before you execute the SQL job in a production environment. For more information, see Cost estimation.
- If you use IntelliJ IDEA, you can submit SQL scripts for automatic cost estimation. For more information, see Develop and submit an SQL script.
- If you use DataWorks, you can also estimate costs.
- The costs of some SQL jobs cannot be estimated, such as SQL jobs that involve external tables.
- The actual costs are subject to final bills.
Best practices of cost estimation
This section provides some cost estimation examples and tips for your reference. You can select a cost-effective billing method based on the information.
- Billing methods for 1 TB of data
The following table describes estimated costs for reference.
Billing method Business scenario Response speed Estimated cost per month Subscription Compute-intensive Within a few minutes 3768 USD Storage-intensive Within a few hours 1177.5 USD Pay-as-you-go 1413 USD (The cost is estimated with the SQL complexity of 1 and the execution frequency of once per day.)If you select the subscription billing method, the costs vary depending on your business type:When you migrate data to the cloud for the first time, we recommend that you select the pay-as-you-go billing method first. Perform a Proof of Concept (POC) test to calculate the approximate number of workers used for your jobs. Then, calculate the number of compute units that you need to purchase based on the number of workers.
- Compute-intensive scenario: In this scenario, a large number of CPU resources are required. 160 compute units are used to process 1 TB of data. The system responds to a request within a few minutes. The estimated cost is 3768 USD per month.
- Storage-intensive scenario: If your jobs are not sensitive to the response speed, we recommend that you purchase a storage plan. About 50 compute units are used to process 1 TB of data. The system responds to a request within a few hours. The estimated cost is 1177.5 USD per month.
- Billing methods for Hadoop users to migrate data to the cloud
Assume that a Hadoop cluster has one controller node and five compute nodes. Each node has 32 cores, equivalent to 32 CPUs. The total number of CPUs for the compute nodes is 160. The estimated cost of the cluster is 3768 USD per month with no discounts or promotional offers applied.
MaxCompute does not require any controller nodes. The performance of MaxCompute is 80% higher than Hive. It frees you from operations and maintenance (O&M), which also reduces costs.
- Mixed billing methods
- Subscription billing method for production businesses, such as hourly extract, transform,
load (ETL), and pay-as-you-go billing method for aperiodic jobs or ad hoc queries
We recommend that you select the subscription billing method for periodic computing jobs that are frequently executed and the pay-as-you-go billing method for aperiodic jobs that are used to process large amounts of data. In pay-as-you-go mode, you can choose not to store data. Instead, you can read data from tables under other accounts. This reduces data storage costs. Authorization is required for computing operations on tables under different accounts. For more information, see Create a project-level role.
- Subscription billing method for aperiodic jobs or ad hoc queries and pay-as-you-go
billing method for production businesses, such as daily ETL
Daily data testing may cause the issue of uncontrollable costs. To avoid this issue, you can add data testing and aperiodic jobs to fixed resource groups. Then, use MaxCompute Management to configure custom development groups and business intelligence (BI) groups. If production jobs are executed only once per day, you can add them to a pay-as-you-go resource group.
- Subscription billing method for production businesses, such as hourly extract, transform, load (ETL), and pay-as-you-go billing method for aperiodic jobs or ad hoc queries
Switching between billing methods
If you select the subscription billing method, you can upgrade or degrade the configurations in the following scenarios: The data volume changes, and the purchased resources are insufficient or become idle. For more information, see Upgrade or downgrade configurations.