> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Compute Resource Pools and Quotas

> Create, edit, and scale instance resource pools, and configure personal quotas, resource administrators, and workload types that can be submitted.

Resource pools are used to organize GPU/CPU instance quotas. Through resource pools, you can allocate computing resources to different teams, users, or task types, and control which resources can be used by development environments, training tasks, and inference services.

## Resource Pool Types and Quota Limits

### Resource Pool Type

Shared resource pools are organized by the platform according to resource type. Dedicated resource pools and exclusive resource pools support creation, editing, and deletion.

| Resource pool type | Management method | Applicable scenarios |
| - | - | - |
| shared resource pool | Quotas are shared among users within the tenant. Authorized users and user-level configurations can be managed on the details page. | General development, debugging, and elastic workloads. |
| dedicated resource pool | Users can be authorized individually and assigned personal quotas. | Reserving resources for specified users or teams, or restricting workload types. |
| exclusive resource pool | Provides exclusive access to entire nodes and displays node health status. | Workloads requiring exclusive use of entire nodes, resource isolation, or more stable scheduling. |

### Dedicated Resource Pool Whole-Machine Validation

Dedicated resource pools require resources to be aligned by whole nodes:

| Resource Type | Whole-Machine Validation Requirement |
| - | - |
| CPU Instance | In whole-machine units of 120 CUs. |
| GPU Instance | In whole-machine units of 8 GPUs. |

When creating, scaling out, scaling in, or purchasing an order with a dedicated resource pool specified, whole-machine validation is required. If the requirements are not met, the operation cannot be submitted.

## Create Resource Pool

Shared resource pools are typically provided by the platform based on resource type. Dedicated resource pools and exclusive resource pools must be created separately according to team usage, isolation requirements, and quota allocation.

Before creating one, ensure that the current account has organization administrator permissions and available instance quota. If you create a dedicated resource pool, the instance quota must also meet the whole-machine validation requirements.

1. Go to **Resources > Instance**.

2. Click **Create Pool**.

3. Configure the resource pool.

   | Parameter | Description |
   | - | - |
   | Region | The region to which the resource pool belongs. |
   | Cluster | The compute cluster to which the resource pool belongs. |
   | Instance | The instance specification used by the resource pool. |
   | Name | The display name of the resource pool. It must be unique within the tenant. |
   | Total Resource Pool Quota | The total amount of resources allocated to the resource pool. |
   | User Default Quota | The user's default personal quota in this resource pool. |
   | Default User Priority | The user's default priority. |
   | Project Group | The project group to which the resource pool belongs. |
   | Type | Select **Dedicated** or **Exclusive**. |
   | Supported Workload Types | The types of tasks that can be submitted to this resource pool. |
   | Resource Pool Scheduling Policy | Supported only for exclusive resource pools and configured separately by resource pool and instance type.<ul><li>**BinPack** tends to schedule workloads onto fewer nodes.</li><li>**Spread** tends to distribute workloads across more nodes.</li></ul>The default is **BinPack**. |
   | Description | A description of the resource pool. |
   | Automatic Faulty Node Rotation | Configurable only for exclusive resource pools. Controls whether faulty nodes in an exclusive resource pool are automatically rotated. |
   | Idle-Time Sharing | Configurable only for exclusive resource pools. Controls whether idle-time sharing is allowed for the exclusive resource pool. |
   | Allow Resource Guarantees | Controls whether resource guarantees can be used in this resource pool. When disabled, users of this resource pool cannot set tasks as resource-guaranteed even if they are granted permission separately. |
   | Freeze Resource Pool | Controls whether the resource pool is frozen. |

4. Click **Create**.

After creation, the resource pool enters the Creating status. Once its status changes to Ready, authorized users can select the resource pool in Develop, Training, or Inference. If the quota of an exclusive resource pool does not meet the whole-node validation requirements, the creation request cannot be submitted. After the resource pool is ready, you can view node health status in its details.

![Compute Resource Pool List](https://mintcdn.com/scitix-adfc65c2/ZqwdmfntBUDyGPkJ/siverse/resources/media/compute-resource-pool-list.png?fit=max\&auto=format\&n=ZqwdmfntBUDyGPkJ\&q=85\&s=aa07672b94c29538e40db59544cdd06a)

## View Resource Pool Details

Go to **Resources > Instance**, then click the name of the target resource pool to open its details page.

![Resource Pool Details](https://mintcdn.com/scitix-adfc65c2/ZqwdmfntBUDyGPkJ/siverse/resources/media/compute-resource-pool-details.png?fit=max\&auto=format\&n=ZqwdmfntBUDyGPkJ\&q=85\&s=1fbc4de2f210732ac8f06af85cfcae4c)

The details page is suitable for making the following assessments and performing the following actions:

| Objective | Description |
| - | - |
| Confirm resource pool availability | View the resource pool status, supported workload types, quota, used, available, and unavailable resources. |
| Manage resource pool settings | Modify the resource pool name, description, supported workload types, or resource policies through **Edit**. |
| Adjust resource pool capacity | Adjust the total resource pool quota through **Resize Quota**. |
| Manage user-level settings | Add users on the **User Info** tab and configure individual quotas, priorities, and resource guarantees. |
| View current workload usage | View workloads currently running in the resource pool, such as development environments, training jobs, and inference services, on the **Running workloads** tab. To handle abnormal resource usage, filter workloads by name, workload type, or user, and stop or delete them after confirming the impact. |
| Query historical workloads | View workloads submitted within the 14 days before the query time, including completed historical records, on the **All workloads** tab. You can filter by **Workload Type**, **Status**, and **Name**. |
| Analyze capacity trends | View trends in quotas and used resources, CPU scheduling rate, unavailable resources, and more on the **Resource Monitor** tab to determine whether the resource pool has been under sustained pressure and whether it needs to be scaled out or its workload distribution adjusted. |
| Trace configuration changes | Trace management actions, such as resource pool settings and user quotas, by operator and time range on the **Operation History** tab to identify the source of configuration changes. |

Resource pool operations are typically performed asynchronously. After you submit a create, scale, conversion, rename, or delete operation, you can check the resource pool status to determine whether the operation has been completed. You can continue using the resource pool once it is ready. If an operation fails, review the on-screen message to identify the cause and contact the platform administrator if necessary.

Dedicated resource pools also display node health status. When all nodes are functioning properly, the status is `healthy`; if any exceptions occur, the page displays details about the affected nodes.

## Adjust Resource Pool Configuration

After creating a resource pool, you can continue to adjust its configuration as needed.

Only organization administrators or resource administrators of the target resource pool can adjust resource pool configurations. On the resource pool list or resource pool details page, you can perform the following operations. Available operations may vary depending on the resource pool type and account permissions.

* **Edit**: Modify the resource pool name, description, supported workload types, or other resource pool configurations.
* **Allow/Disallow Guarantee**: Control whether users are allowed to use Guarantee in the resource pool. When disabled, users in this resource pool cannot set tasks to Guarantee, even if they have been granted permission individually.
* **Default User Priority**: Adjust the default user priority for the resource pool.
* **User Default Quota**: Adjust the default quota for newly authorized users or users who follow the default configuration in the resource pool.
* **Adjust Project Group**: Modify the Project Group to which the resource pool belongs.
* **Delete**: Delete resource pools that are no longer in use. Before deletion, ensure that the resource pool contains no quotas, user configurations, or workloads that still need to be retained or are in use.

If you only need to add users to the resource pool, click **Create User**. To adjust the configuration of an existing user, go to the **User Info** tab.

**User Default Quota** defines the rules used for subsequent allocations or when following the default configuration. It does not mean that the individual quotas of all existing users have been changed uniformly. To verify an individual user’s actual quota, go to the **User Info** tab.

## Manage Authorized Users and Personal Quotas

Resource pools support user-based authorization management and configuration of individual quotas, priorities, and resource guarantees. Quotas in a shared resource pool are still consumed collectively by users within the tenant; user-level settings control each user’s available quota and scheduling policy in that resource pool.

> [!TIP]
>
> Personal quota limits the amount of resources a user can use in the resource pool. If the total quota of the resource pool is insufficient, tasks may fail to be scheduled even if the user's personal quota has not been fully used.

### View and manage authorized users

Only organization administrators or resource administrators of the target resource pool can manage authorized users and personal quotas. On the resource pool details page, open the **User Info** tab.

![Authorized users in a resource pool](https://mintcdn.com/scitix-adfc65c2/ZqwdmfntBUDyGPkJ/siverse/resources/media/resource-pool-user.png?fit=max\&auto=format\&n=ZqwdmfntBUDyGPkJ\&q=85\&s=4bc92cd215d28d2614fa9891e8b03a33)

When managing user-level configurations, first note the following information:

| Objective | Information to Monitor |
| - | - |
| Control user quotas | View used resources and, based on the **Config Mode** and **Quota**, determine whether the user has reached the available quota limit. |
| Control task scheduling policies | Use **Max Priority** and **Resource Guarantee** to control the scheduling capabilities available to users within the resource pool. Loads created in pay-as-you-go resource pools are non-preemptible by default and do not support editing the resource guarantee configuration. |
| Investigate resource usage | Use **Usage History** to view a user's historical usage in the resource pool and determine whether resources have been occupied for an extended period. |

### Add Resource Pool Authorized Users

![Add Resource Pool Authorized User](https://mintcdn.com/scitix-adfc65c2/ZqwdmfntBUDyGPkJ/siverse/resources/media/add-resource-user.png?fit=max\&auto=format\&n=ZqwdmfntBUDyGPkJ\&q=85\&s=2dbdcb42c0376ca165813f26c9d9f46b)

After clicking **Create User**, select one of the following methods to add authorized users in batches:

* **Select from user list**: Select the users to authorize and configure individual quotas.
* **Paste name list**: Paste usernames separated by commas or line breaks. Each line corresponds to a group of users and its configuration. You can set **Instance**, **Config Mode**, **User Quota**, **Max Priority**, and **Resource Guarantee**; to use different configurations, add a new line and configure them separately.

User quotas configured in this way are maintained separately by the administrator. Subsequent changes to the resource pool's default quota will not overwrite these users' current quotas.

### Other Actions

After searching for a username on the **User Info** tab, you can also perform the following actions:

* **Batch Update**: Adjust the quota, **Max Priority**, or **Resource Guarantee** settings for multiple users at once.
* **Export**: Select **Export CSV List** to download user information, or select **Copy Names to Clipboard** to copy usernames.
* **Edit**: Modify the quota settings for an individual user.
* **Delete**: Remove authorized users from the resource pool.

## Scaling Resource Pools

You can adjust the total quota of a resource pool by scaling it out or in. Whether scaling is supported depends on the resource pool type, resource pool status, and the current account permissions.

Before making adjustments, ensure that the current account has organization administrator permissions or is a resource administrator for the target resource pool.

In the resource pool list or on the resource pool details page, click **Resize Quota** for the relevant resource pool to adjust its total quota.

Scaling supports **by quantity** or **Specify Nodes**.

* During scale-out, quota is migrated from the shared resource pool by default. You can also specify another resource pool of the same resource type as the quota source. Before submitting, ensure that the source resource pool has sufficient available quota.

* Before scaling down, ensure that the target resource pool does not contain used resources exceeding the total capacity after scale-down. If resources are occupied by Develop, Training, or Inference, the scale-down operation may fail.

Scaling is an asynchronous operation. During the operation, the relevant resource pool enters the updating state and returns to the ready state after completion.

After scaling is complete, check the resource pool status, actual nodes, available resources, and schedulable capacity to confirm that the added or released quota is available for tasks. If the change has not yet been completed, track the result of the current operation first to avoid repeatedly submitting similar scaling operations.

## Convert Resource Pool Type

Dedicated resource pools and exclusive resource pools can be converted into each other.

Before conversion, ensure that the current account has organization administrator permissions or is the resource administrator of the target resource pool, and meets the following conditions:

* No update, delete, or other resource operations are in progress for the target resource pool.
* The converted resource pool type meets the requirements of the use case.
* When converting to a dedicated resource pool, the quota must meet the whole-machine validation requirements.

In the resource pool list or on the resource pool details page, open More Actions and select the conversion action for the corresponding resource pool type.

During the conversion, the resource pool enters the updating state. Once its status returns to Ready, you can continue submitting tasks.

## Consolidate Dedicated Resource Pool Fragments

After a dedicated resource pool has been running for an extended period, resource fragmentation may occur: multiple small workloads become distributed across high-specification nodes, preventing large-scale training or inference tasks from obtaining contiguous resources.

Defragmentation consolidates distributed workloads onto a small number of nodes, freeing up completely idle nodes.

Before the cleanup, you can go to the dedicated resource pool details page to view node and migration information:

* **Node Info**: Locate nodes by idle-first priority, status, node name, or workload name, and view node status, hosted workloads, and resource usage. When resource distribution on a node needs to be addressed, use the available page options to migrate resources, defragment resources, or stop scheduling.
* **Migration Records**: View resource migration records initiated from the node view, including the status, direction, migration mode or node, evicted workloads, and initiator. Resource allocation initiated by directly editing the resource pool quota is not included in these records.

### Filter Criteria

* The resource pool type is dedicated.
* The resource pool status is `ready` or `failed`.
* No cleanup task is currently running in the resource pool.
* The current account is a tenant administrator or resource pool administrator.

### Organizing Process

1. Go to the dedicated resource pool details page.

2. Click the **Node Info** tab, and then click **Defragment**.

   ![Dedicated Resource Pool Defragmentation](https://mintcdn.com/scitix-adfc65c2/ZqwdmfntBUDyGPkJ/siverse/resources/media/resource-pool-defragmentation.png?fit=max\&auto=format\&n=ZqwdmfntBUDyGPkJ\&q=85\&s=cbfabf7acdf31ce3ff211bc10e022e8a)

3. In the dialog box, select the workload types to be defragmented and the maximum number of rounds.

4. Run a trial preview to review the list of workloads expected to be adjusted.

5. After confirmation, start defragmentation and view the results.

### Risks and Limitations

Defragmentation uses a conservative reserve-first, migrate-later strategy. The platform evicts and recreates the original Pod only after the target node has successfully reserved resources. If reservation fails, the target node encounters an exception, or any other unexpected situation occurs, the platform terminates the migration.

A single consolidation run does not guarantee that all workloads can be migrated successfully. Insufficient resources on target nodes, insufficient quota, Pod status changes, node exceptions, or a timeout during a consolidation round may cause some workloads to remain incomplete or be skipped. Pods that remain incomplete or are skipped do not affect the processing results of other Pods.

If you choose to stop the workload, the stop action terminates the corresponding training task, with the same effect as manually stopping it. If the task is configured with a checkpoint, it can later be resumed from the checkpoint.

## FAQ

> **Why can't I see a resource pool when creating a task?**
>
> Ensure that the current account is authorized to use the resource pool and that the resource pool supports the current task type. A resource pool can restrict the supported workload types. If the current task type is not supported, you may be unable to select the resource pool when creating a task, or the submission may be rejected during quota validation.

> **Why might a task still fail to be scheduled even when my personal quota is sufficient?**
>
> Personal quota only limits the amount of resources a user can use within the resource pool. Whether a task can be scheduled also depends on the resource pool's total quota, available resources, instance specification, workload type restrictions, and resource pool status.

> **When do I need to scale out a resource pool?**
>
> When the target resource pool has insufficient total quota or available quota, resulting in queued tasks, submission failures, or an inability to allocate sufficient personal quota to users, consider scaling out the resource pool. Before scaling out, ensure that the source resource pool has sufficient available quota.

> **Why does resource auth check failed occur when submitting a task?**
>
> Resource pools support workload type configuration. After configuration, only the selected workload types can use the resource pool. If the Task Type is not allowed by the resource pool, the submission will be rejected during quota validation, and an error similar to the following may occur:
>
> ```text theme={null}
> resource auth check failed, workload type XXX is not allowd to use resource pool XXX
> ```
>
> If you need to submit tasks in this resource pool, modify the resource pool's workload type configuration.

## Related Documentation

* [Prepare Instance](/siverse/resources/prepare-compute-resources.md)
* [View Resource Usage](/siverse/resources/view-resource-usage.md)
* [View Task Resource Usage](/siverse/resources/view-task-resource-usage.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.