This topic describes the basic resources, billing rules, usage notes, and considerations for MaxCompute pay-as-you-go.
- Computing resources are shared. These resources are consumed to execute computing jobs, such as SQL statements, user-defined functions (UDFs), MapReduce jobs, Spark jobs, Lightning jobs, and Graph jobs. Computing jobs must compete for these resources. You cannot specify resources for computing jobs. No limits are imposed on these resources.
- Storage resources are shared and automatically scaled. No limits are imposed on these resources. MaxCompute tables and resources consume storage resources.
- Resources for data uploads and downloads are shared. You cannot specify resources for upload and download jobs. No limits are imposed on these resources. However, both upload and download jobs must compete for these resources. For example, these resources are consumed when you use the Tunnel Upload and Download commands.
The resources of MaxCompute pay-as-you-go are charged based on the pay-as-you-go billing method. The resources are charged based on the following rules:
- Computing resources: You are charged for the computing resources that you use to execute computing jobs. For more information, see Billing for Computing.
- Storage resources: You are charged only for the resources that are used to store tables. MaxCompute compresses your data for storage. You are charged for the data volume after compression. Data is typically compressed to about 20% of the original data volume. For more information, see Storage pricing (pay-as-you-go).
- Resources for data uploads: You are not charged for the resources that are used to upload data to MaxCompute.
- Resources for data downloads: You are charged only for the resources that are used to download data over the Internet. For more information, see Download pricing(Pay-As-You-Go).
- For more information about how to activate MaxCompute and purchase resources through standard pay-as-you-go, see Activate MaxCompute.
- Resources purchased through standard pay-as-you-go can be used by all projects that reside in the same region where the resources are purchased.
- If a project uses a subscription-based resource package and you have purchased a pay-as-you-go resource package, you can switch the resource package of the project to the pay-as-you-go resource package. If a project uses a pay-as-you-go resource package and you have purchased a subscription-based resource package, you can switch the resource package of the project to the subscription-based resource package.
- No limits are imposed on the number of resources in pay-as-you-go. The computing resources purchased through standard pay-as-you-go are from a shared resource pool. For example, a job requires 1,200 CUs. If the current resource pool has sufficient resources, the job can use 1,200 CUs. If all the resources in the current resource pool are occupied or the resources that remain are insufficient for the job, the job must wait for the resources released or compete for the remaining resources. As a result, the execution duration is prolonged.