MaxCompute:Consumption control

MaxCompute pay-as-you-go resources are elastic and scale on demand, with no preset limits on resource usage. To avoid unexpected costs, monitor the consumption of your computing tasks. MaxCompute provides the following consumption control features:

Configuration

You can set a per-statement resource limit in the following ways:

• Project-level setting

  The project owner or a user with the Super_Administrator role must run the following command to enable or disable the per-statement resource limit.

  -- Enable the per-statement resource limit.
  SETPROJECT odps.sql.metering.value.max=<m_value>;
  -- Disable the per-statement resource limit.
  SETPROJECT odps.sql.metering.value.max;

  The m_value parameter is the maximum consumption threshold for a single SQL statement. It is calculated as SQL read volume (GB) × SQL complexity and is not a monetary amount.

  Note

  A project's per-statement consumption is constrained by m_value. If a statement's estimated consumption exceeds this m_value, the system blocks its execution.

• Session-level setting

  To enable a per-statement resource limit for a single execution, submit the following command along with your SQL statement. If you do not include this command, the limit is disabled. This setting is valid only for the current execution.

  SET odps.sql.metering.value.max=<m_value>;

Recommendations

Follow these best practices:

• Set a project-level m_value based on historical SQL consumption and your expected spending.

  • You can download daily detailed metering data and calculate the resource consumption for SQL tasks (tasks with a data classification of ComputationSql) at the project level. Resource consumption is calculated as SQL read volume (GB) × SQL complexity. Determine a suitable value based on the highest normal daily consumption, factoring in business fluctuations.

  • Alternatively, you can convert compute consumption to a cost . Based on your business needs, determine an acceptable cost, and then convert that cost back into a consumption value: .

• Set a project-level limit first, then use a session-level m_value limit for specific, exceptional SQL statements.

  Note

  • Before setting a session-level limit, confirm that the specific SQL statement truly requires it to avoid misuse.

  • If both project-level and session-level limits are set, the session-level limit takes precedence.

    For example, if a project's m_value is set to 100, but a specific SQL statement within that project has a session-level m_value of 200, the statement is blocked only if its estimated consumption exceeds 200, not 100. Other SQL statements without a session-level limit still adhere to the project's limit of 100 and are blocked if their estimated consumption exceeds 100.

• Setting either a project-level or session-level limit affects task execution. Use these limits with a task failure alert feature, such as DataWorks intelligent monitoring, to detect task failures promptly and intervene manually. This prevents critical tasks from being blocked and impacting business operations.

Configuration

You can set a daily cumulative spend limit for a project using the following command. Only the project owner or a user with the Super_Administrator role can run this command.

SETPROJECT odps.costcontrol.rule={"byDate":{"sql":<Limit>}};

• byDate: Sets a daily limit. The cumulative consumption is calculated for the period from 00:00:00 to 23:59:59 (UTC+8). The counter resets on the next day.

• Limit: The daily cumulative spending threshold for standard SQL in the project, specified in USD. This consumption tracking does not include any discounts or promotions.

  Note

  Cost per SQL statement = Scanned data volume (GB) × Complexity × 0.0438. In the Saudi Arabia (Riyadh) region, which is operated by a partner, the standard SQL billing rate is 0.05256 USD/GB.

Usage notes

After setting the limit using this command, be aware of the following rules: