MaxCompute:Manage quotas for computing resources

Configuration procedure

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

2. In the left navigation pane, choose Workspace > Quota Management.

3. On the Quota Management page, for the subscription level-1 quota that you want to configure, click Quota Configuration in the Actions column.

4. Configure basic quota settings.

   1. On the Basic Configurations tab of the Quota Configuration page, click Edit Basic Configurations to add a level-2 quota and configure its basic parameters, including exclusive, CU limit per job, priority, non-reserved CUs, and scheduling policy.

      On the Basic Configurations tab, you can also click Delete in the Actions column for a quota to delete the level-2 quota.

      Note

      After you delete a level-2 quota, it is removed from all quota resource configuration plans. The CUs specified by minCU and the elastic reserved CUs are returned to the default level-2 quota. To make adjustments, you can update the configuration plans on the Scaling Configuration tab.

   2. Click Edit Basic Configurations and configure the following parameters for the level-2 quota:

      Parameter	Description
      Quota Name	Add a level-2 quota. Click Add Level-2 Quota, enter a Quota Name, and select a Type. The Quota Name must be a custom name that starts with a letter and contains only letters, digits, and underscores (_).
      Type	The Type can be one of the following. Select a type as needed. Batch: A quota used to run batch processing jobs. Interactive: A quota dedicated to running MaxCompute Query Acceleration (MCQA) jobs. You do not need to set this as the project's default computing quota. If a project's default computing quota is a subscription batch processing quota, jobs that hit query acceleration are automatically scheduled to an interactive quota. If multiple interactive quotas exist, MCQA jobs are scheduled to the earliest created interactive quota by default. You can use quota rules to schedule MCQA jobs from different projects to different interactive quotas. For more information about quota rules, see Quota rules.
      Reserved CUs [minCU,maxCU]	The number of subscription reserved CUs. The number of reserved CUs for a level-1 quota is the number of subscription CUs you purchased (minCU=maxCU). To scale out or scale in, you must upgrade or downgrade the quota. This parameter cannot be edited here. The minCU and maxCU for a level-2 quota are defined as follows: minCU is the guaranteed value, and maxCU is the upper limit. If maxCU is greater than minCU, the level-2 quotas are in shared mode. If the requested CU amount is greater than the min value, idle and non-exclusive CUs from other quotas can be preempted. The sum of minCU values for all level-2 quotas equals the minCU value of the level-1 quota. The value of minCU must be less than or equal to maxCU, which must be less than or equal to the minCU value of the purchased level-1 quota. Note You cannot set minCU to 0 at this time. The minCU and maxCU of the default level-2 quota cannot be edited. The minCU value is the minCU of the level-1 quota minus the sum of the minCU values of all custom level-2 quotas. The maxCU value is equal to the maxCU of the level-1 quota. If you add a new quota and multiple scaling configuration plans exist, the new quota is added to all plans. For plans other than the current effective plan, the default reserved minCU is 1. This is deducted from the default subscription level-2 quota. To adjust the CU amount, edit and update each configuration plan on the Scaling Configuration tab. Important For a new quota, this configuration applies only to the current effective configuration plan.
      Elastic reserved CUs	The number of elastic reserved CUs purchased on an hourly basis. For more information about the billing of elastic reserved CUs, see Computing fees (hourly billing). The number of elastic reserved CUs for a level-1 quota is the number of CUs you need to purchase. The default is 0. The maximum value is the number of subscription reserved CUs purchased for the quota, and cannot exceed 10,000 CUs. This is also subject to inventory limits. Inventory is checked when you configure a scale-out. The configured scale-out capacity must be at least 50 CUs or in multiples of 50. The number of elastic reserved CUs for a level-2 quota is defined as follows: The sum of elastic reserved CUs for all level-2 quotas equals the number of elastic reserved CUs for the level-1 quota. The number of elastic reserved CUs for the default level-2 quota cannot be edited. It is the number of elastic reserved CUs for the level-1 quota minus the sum of elastic reserved CUs for all custom level-2 quotas. If you add a new quota and multiple scaling configuration plans exist, the new quota is added to all plans. For plans other than the current effective plan, the default elastic reserved CUs is 0. To adjust the CU amount, edit and update each configuration plan on the Scaling Configuration tab. Important For a new quota, this configuration applies only to the current effective configuration plan.
      Exclusive	Specifies whether the quota is strongly exclusive. If a quota is exclusive, its CUs are not used by other quota groups even when idle. This can only be configured for level-2 quotas. If the level-2 quota type is Interactive, this parameter is set to exclusive by default and cannot be modified. This is suitable for quota groups that run services such as BI or ALGO, which may be used at any time. It prevents the quota from being occupied by other quotas for a long time. When a quota's max value is greater than its min value, it may occupy other idle quotas.
      CU limit per job	Sets a concurrent CU limit for jobs that run in this quota. Leave it empty for no limit. Set it to 0 for an absolute restriction. You can enter a positive integer for a reasonable limit. This parameter is unavailable by default when the level-2 quota type is interactive. This is useful to prevent a single job from occupying many CUs for a long time, which causes other jobs to wait for resources. You can also set a limit at the job level. Use the set odps.task.max.concurrent.cu=<CU_Amount>; command before your code. The job-level configuration has a higher priority than the quota-level configuration.
      Enable priority	The priority feature. For more information, see Job priority. Jobs that run on this quota are prioritized. Enabling it at the project level also takes effect. This parameter is unavailable by default when the level-2 quota type is Interactive.
      Non-reserved CUs	The number of subscription non-reserved CUs. The number of non-reserved CUs for a level-1 quota is the number of subscription non-reserved CUs you purchased. To scale out or scale in, you must upgrade or downgrade the quota. You cannot scale out if the inventory is low. This parameter cannot be edited here. The number of non-reserved CUs for a level-2 quota is defined as follows. The sum of non-reserved CUs for all level-2 quotas equals the number of non-reserved CUs for the level-1 quota. The number of non-reserved CUs for the default level-2 quota cannot be edited. It is the number of non-reserved CUs for the level-1 quota minus the sum of non-reserved CUs for all custom level-2 quotas.
      Scheduling policy	MaxCompute level-2 quota scheduling policies include FAIR and FIFO. FAIR (fair scheduling) For jobs with the same priority, resources are allocated evenly to all jobs submitted at the same time. For jobs with different priorities, resources are first allocated evenly to higher-priority jobs. If resources remain, they are then allocated evenly to lower-priority jobs. FIFO (first in, first out) For jobs with the same priority, resources are allocated to the jobs that are submitted first. For jobs with different priorities, resources are allocated to higher-priority jobs, even if lower-priority jobs were submitted earlier. Select a suitable scheduling policy based on your business needs. You cannot set a scheduling policy for interactive level-2 quotas. For more information, see Quota scheduling policies for computing resources. Important Since May 24, 2023, the default scheduling policy for new level-2 quotas 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.

   3. Click OK.

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 contains the reserved CU and elastic reserved CU configurations for a level-1 quota and all its level-2 quotas. You can combine multiple configuration plans with time-based management. This feature is often used for scenarios that require different configurations at different times of the day. For example, if a level-2 quota has different CU requirements for the 00:00-08:00 and 08:00-24:00 periods, you can create two quota configuration plans and schedule them using time-based management.

   Note

   You can add up to 48 resource configuration plans. Each plan can have different settings, which lets you enable different plans at different times of the day.

   1. On the Quota Configuration page, on the Scaling Configuration tab, click Add Configuration Plan.

   2. On the Add Configuration Plan page, you can configure the following quota parameters.

      Parameter	Description
      Reserved CUs [minCU,maxCU]	The number of subscription reserved CUs. The number of reserved CUs for a level-1 quota is the number of subscription CUs you purchased (minCU=maxCU). To scale out or scale in, you must upgrade or downgrade the quota. This parameter cannot be edited here. The minCU and maxCU for a level-2 quota are defined as follows: minCU is the guaranteed value, and maxCU is the upper limit. If maxCU is greater than minCU, the level-2 quotas are in shared mode. If the requested CU amount is greater than the min value, idle and non-exclusive CUs from other quotas can be preempted. The sum of minCU values for all level-2 quotas equals the minCU value of the level-1 quota. The value of minCU must be less than or equal to maxCU, which must be less than or equal to the minCU value of the purchased level-1 quota. Note You cannot set minCU to 0 at this time. The minCU and maxCU of the default level-2 quota cannot be edited. The minCU value is the minCU of the level-1 quota minus the sum of the minCU values of all custom level-2 quotas. The maxCU value is equal to the maxCU of the level-1 quota.
      Elastic reserved CUs	The number of elastic reserved CUs purchased on an hourly basis. The number of elastic reserved CUs for a level-1 quota is the number of CUs you need to purchase. The default is 0. The maximum value is the number of subscription reserved CUs purchased for the quota, and cannot exceed 10,000 CUs. This is also subject to inventory limits. Inventory is checked when you configure a scale-out. The configured scale-out capacity must be at least 50 CUs or in multiples of 50. The number of elastic reserved CUs for a level-2 quota is defined as follows: The sum of elastic reserved CUs for all level-2 quotas equals the number of elastic reserved CUs for the level-1 quota. The number of elastic reserved CUs for the default level-2 quota cannot be edited. It is the number of elastic reserved CUs for the level-1 quota minus the sum of elastic reserved CUs for all custom level-2 quotas.

   3. Click OK to add the configuration plan.

   4. On the Scaling Configuration tab, click Apply Immediately in the Actions column of the new configuration plan. Alternatively, you can schedule the plan to take effect later in Time-based Management.

   5. (Optional) Perform other operations related to the resource configuration plan:

      • View a configuration plan: Click the icon to the left of a configuration plan name to view the plan details.

      • To edit a configuration plan, click Edit in the Actions column. If the plan is currently in effect, you must also click Apply Immediately in the Actions column to apply the updated configuration.

        Note

        You can click Apply Immediately to apply a configuration plan. Note that if a time-based schedule is set, your manual selection will be overwritten at the next time slot. To ensure your manually applied plan remains in effect, you must clear all time-based settings. This action ensures that your selected plan takes effect immediately and is not overwritten.

      • To delete a configuration plan, on the Quota Scaling Configuration tab, click Delete in the Actions column for the plan.

        Note

        The Default plan and the currently effective plan cannot be deleted.

      • To clone a configuration plan: On the Quota Scaling Configuration tab, in the Actions column of the target configuration plan, click > Clone. For the Default plan, click Clone directly.

   6. Time-based management.

      You can set different quota configuration plans to be enabled at different times of the day. This lets you implement time-based management of quota configurations.

      Note

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

      1. On the Scaling Configuration tab of the Quota Configuration page, in the Time-based Management section, click Edit Time Plan.

      2. Click Add Effective Period and select an Effective Start Time (UTC+8) and a Configuration Plan.

         • There is only one overall time plan. The default start time is 00:00, which cannot be modified or deleted. The corresponding configuration plan is Default, which can be modified. If no other start times are added, the same configuration plan is enabled for the entire day.

         • You can enable different configuration plans on the hour and half-hour. A configuration plan can be enabled multiple times.

   7. Time-based scaling preview: You can select a level-2 quota to view the CU allocation trend chart for different time periods.

   8. Scaling configuration global view: This view displays the details of all configuration plans in a global view table. You can view the minimum and maximum reserved CUs and elastic reserved CUs for all quotas in each time-based period.