MaxCompute:Compute resources - Quota management

Basic configuration

Basic configuration covers adding or deleting Level-2 quotas and setting parameters such as exclusivity, the single-job CU limit, job priority, non-reserved CUs, the scheduling policy, reserved CUs, Elastic Reserved CUs, and AutoscaleLimitCU. These settings apply only to the currently active configuration plan. If you do not need time-based management, this configuration is sufficient.

Each Level-1 quota supports up to 100 Level-2 quotas. Plan your quota structure based on your business scenarios.

Scaling configuration

Scaling configuration lets you set different minimum and maximum reserved CUs, Elastic Reserved CUs, and AutoscaleLimitCU values for a quota at different times.

Procedure

1. Log in to the MaxCompute console and select a region in the upper-left corner.

2. In the left-side navigation pane, choose Manage Configurations > Quotas .

3. On the Quotas page, click Quota Configuration in the Actions column of the target quota.

   This operation is supported only for quotas for which the Billing Method is Subscription.

4. Configure basic quota settings

   1. On the Quota Configuration page, select the Basic Configurations tab and click Edit Basic Configurations.

      The following table describes the parameters.

      Parameter	Description
      Quota Name	Enter a custom name. The name must start with a letter and can contain letters, digits, and underscores (_).
      Type	Batch: a quota used for running batch jobs. Interactive: a quota dedicated to running MaxQA (query acceleration) jobs. You do not need to set it as the default computing quota for a project. If the default computing quota for a project is a subscription batch quota, jobs that trigger query acceleration are automatically scheduled to run in an interactive quota. Note This automatic scheduling behavior applies to MCQA. In MaxQA mode, you must explicitly specify the interactive quota group name in the client or connection string. Automatic quota routing is not supported. If multiple interactive quotas exist, MCQA (query acceleration 1.0) jobs are scheduled to the first-created interactive quota by default. You can use quota rules to schedule MCQA jobs from different projects to different interactive quotas. In MaxQA (query acceleration 2.0) mode, you must explicitly specify the quota group name because automatic quota routing is not supported.
      Reserved CUs [minCU,maxCU]	The monthly reserved CUs. minCU is the guaranteed value and maxCU is the upper limit. The reserved CUs for a level-1 quota are the total CUs purchased with a subscription (minCU=maxCU). You can only scale this value up or down by upgrading or downgrading the quota. You cannot edit this value here. If maxCU > minCU, level-2 quotas are in a shared mode. If the requested CUs exceed the minCU value, idle resources from other non-exclusive quotas can be preempted. The sum of the minCU values for all level-2 quotas must equal the minCU value of the level-1 quota. For a level-2 quota, minCU must be less than or equal to maxCU, and maxCU must be less than or equal to the purchased minCU value of the level-1 quota. The minCU and maxCU values of the default level-2 quota cannot be edited: minCU of default level-2 quota = [minCU of level-1 quota] - [sum of minCU values of custom level-2 quotas] The maxCU value is equal to the maxCU value of the level-1 quota. The minCU of a level-2 quota cannot currently be set to 0. For a new quota: This configuration applies only to the currently active plan. If multiple scaling plans exist, the new quota is added to all of them. For plans other than the active one, the default reserved minCU is set to 1 (deducted from the default level-2 subscription quota). To adjust the CU amount, edit each plan on the Scaling Configuration tab.
      Elastically Reserved CUs	Pay-as-you-go elastic CUs. For more information about the billing of elastic reserved CUs, see Compute fees (pay-as-you-go). For a level-1 quota, this parameter specifies the number of CUs to pre-purchase. The default value is 0. The maximum value is the lesser of the subscription reserved CUs for the quota or 10,000 CUs. The value is also subject to inventory availability, which is checked during scaling. The minimum scale-up amount is 50 CUs, and the value must be increased in multiples of 50. The elastic reserved CUs for a level-2 quota are defined as follows: The sum of elastic reserved CUs for all level-2 quotas must equal the elastic reserved CUs of the level-1 quota. The elastic reserved CUs of the default level-2 quota cannot be edited. This value is calculated by subtracting the total elastic reserved CUs of custom level-2 quotas from the elastic reserved CUs of the level-1 quota. For a new quota: This configuration applies only to the currently active plan. If multiple scaling plans exist, the new quota is added to all of them. For plans other than the active one, the default value for elastic reserved CUs is 0. To adjust the CU amount, edit each plan on the Scaling Configuration tab.
      AutoScale CUs	The maximum number of resources available for auto scaling to handle workload fluctuations. For more information about the billing of auto scaling, see Compute fees (pay-as-you-go). Level-1 quota: Auto scaling is disabled by default. The default value of Auto Scaling Limit CUs (AutoscaleLimitCU) is 0. The Auto Scaling Limit CUs can be set in increments of 10. The maximum value is the reserved CU value of the level-1 quota. When auto scaling is enabled, the quota always occupies the reserved reserved CU + elastic reserved CU resources during the effective period of the configuration plan. To meet job workload demands, it also uses additional auto scaling CUs, the number of which is greater than 0 and less than or equal to AutoscaleLimitCU. Level-2 quota: If auto scaling is enabled for a level-1 quota, it is enabled for all of its level-2 quotas by default. You can set the Auto Scaling Limit CUs for each level-2 quota separately. The value for a batch quota can be set in increments of 10 CUs, and for an interactive quota in increments of 25 CUs. The value must be in the range of [0, AutoscaleLimitCU of the level-1 quota]. All level-2 quotas share auto scaling resources, which are automatically allocated based on the workload of each level-2 quota. In practice, the total auto-scaled CUs used by all level-2 quotas under a level-1 quota equals the auto-scaled CUs used by the level-1 quota and does not exceed its auto scaling limit.
      Exclusive or Not	Specifies whether the quota is strictly exclusive, meaning its CUs cannot be used by other quota groups even when idle. This parameter can only be configured for level-2 quotas. If the level-2 quota type is Interactive, this parameter is enabled by default and cannot be modified. This setting is suitable for quota groups running BI or ALGO services. These types of jobs may be initiated at any time, and this setting prevents their resources from being occupied by other quotas for extended periods, which can happen when a quota's max value is greater than its min value.
      Maximum Number of CUs for a Single Job	Specifies the CU concurrency limit for jobs in this quota. An empty value or 0 means no limit. Enter a positive integer to set a limit. This parameter is not available when the level-2 quota type is Interactive. This setting prevents a single job from occupying a large number of CUs for a long time, which would cause other jobs to wait for resources. You can also set a limit at the job level by running the set odps.task.max.concurrent.cu=<CU_amount>; command before your code. Job-level configurations have a higher priority than quota-level configurations.
      Enable Priority	Enables the job priority feature. For more information, see Job priorities. Jobs running in this quota will be prioritized. The same effect occurs if priority is enabled at the project level. This parameter is not available when the level-2 quota type is Interactive.
      Non-reserved CUs	The monthly non-reserved CUs. The non-reserved CUs for a level-1 quota are the amount purchased with a subscription. You can only scale this value up or down by upgrading or downgrading the quota. You cannot edit this value here. Scaling up is currently unavailable due to limited inventory. The non-reserved CUs for a level-2 quota are defined as follows: The sum of non-reserved CUs for all level-2 quotas must equal the non-reserved CUs of the level-1 quota. The non-reserved CUs of the default level-2 quota cannot be edited. This value is calculated by subtracting the total non-reserved CUs of custom level-2 quotas from the non-reserved CUs of the level-1 quota.
      Scheduling Policy	MaxCompute level-2 quota scheduling policies include FAIR and FIFO. FAIR (fair scheduling) For jobs with the same priority, resources are allocated equally among all jobs submitted at the same time. For jobs with different priorities, resources are first allocated equally to higher-priority jobs. If resources remain, they are then allocated equally to lower-priority jobs. FIFO (first-in-first-out) For jobs with the same priority, resources are allocated to the first submitted job. For jobs with different priorities, resources are allocated to higher-priority jobs, even if they are submitted after lower-priority jobs. Select a scheduling policy based on your business needs. This setting is not supported for interactive level-2 quotas. For more information, see Scheduling policies for computing resource quotas. Important Starting from May 24, 2023, the default scheduling policy for new level-2 quotas created in the China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), and China (Chengdu) regions is FIFO. For level-2 quotas created in these regions before this date, the default scheduling policy is FAIR.

   2. Delete a quota

      On the Quota Configuration page, select the Basic Configurations tab, and then click Delete in the Actions column of the target quota.

      After a Level-2 quota is deleted, it is removed from all resource configuration plans. Its minCU and Elastic Reserved CUs are returned to the default Level-2 quota. To make adjustments, edit the configuration plans on the Scaling Configuration tab.

5. Configure quota scaling

   After you purchase a subscription MaxCompute project, each Level-1 quota has a default resource configuration plan named Default.

   Each resource configuration plan specifies the reserved CUs, Elastic Reserved CUs, and AutoscaleLimitCU for a Level-1 quota and all its Level-2 quotas. You can create multiple plans and use time-based management to switch between them at different times of the day. For example, if a Level-2 quota has different CU requirements during the 00:00–08:00 and 08:00–24:00 periods, you can create two plans and schedule them accordingly.

   Note

   You can add up to 48 resource configuration plans. Each plan can have a different configuration to be enabled at different times of the day.

   1. On the Quota Configuration page, select the Scaling Configuration tab.

   2. On the Scaling Configuration tab, click Add Configuration Plan. In the Add Configuration Plan dialog box, enter a Configuration Plan Name and configure the Reserved CUs [minCU,maxCU], Elastically Reserved CUs, and AutoScale CUs for the level-2 quota.

      For more information about the parameters, see the preceding parameter description table.

   3. Click OK to add the plan.

   4. On the Scaling Configuration tab, click Apply Immediately in the Actions column of the target plan to apply it immediately. You can also use existing plans when configuring Scheduled Scaling Management.

      You can click Apply Immediately for any plan. Note that if time-based scheduling is configured, the manually applied plan will be overridden by the next scheduled plan. To manually apply a plan and prevent it from being overridden, you must clear all other time-based settings.

6. (Optional) Manage a configuration plan

   • View a configuration plan

     On the Scaling Configuration tab, click the icon to the left of a Configuration Plan Name to expand and view the plan details.

   • Edit a configuration plan

     On the Scaling Configuration tab, click Edit in the Actions column of the target plan to update it.

     If the plan is currently in effect, you must click Apply Immediately in the Actions column after editing to apply the new configuration.

   • Delete a configuration plan

     On the Scaling Configuration tab, click Delete in the Actions column of the target plan to delete it.

     You cannot delete the Default plan or the plan that is currently in effect.

   • Clone a configuration plan

     On the Scaling Configuration tab, click Clone in the Actions column of the target plan to create a copy of it.

7. Configure time-based management

   Schedule different configuration plans to activate at specific times of the day.

   Note

   Time-based scheduling may have a delay of up to 5 minutes.

8. On the Scaling Configuration tab, click Edit Time Plan in the Scheduled Scaling Management section.

9. Click Add Effective Period, and then select an Effective start time and a Configuration Plan.

   Note

   • There is only one overall time plan with a default start time of 00:00, which cannot be modified or deleted. It uses the Default configuration plan by default, but you can change it. If you do not add other start times, the same configuration plan applies throughout the day.

   • You can activate different configuration plans on the hour and half-hour. A single configuration plan can be activated multiple times.