All Products
Search

This Product

    Platform For AI:Scheduling Configuration

    Document Center

    Platform For AI:Scheduling Configuration

    Last Updated:Jun 20, 2026

    Workspace administrators can configure resource usage rules for modules within a workspace based on different business needs and scenarios. These rules include usage limits, priority settings, auto shutdown policies, and cost control strategies.

    Note

    In these configurations, non-workspace members are users who have not been added to the workspace by an administrator but have been granted corresponding RAM permissions by the root account. As a result, they can still use resources and submit tasks. You can define separate constraints for these users.

    Resource usage

    Configure the scope of resource quota usage for the current workspace, such as limiting usable modules, roles, and quotas. If you do not require fine-grained control, skip this configuration to freely use all product modules in the current workspace.

    • Resource usage modules: Restrict the modules (DSW, DLC) that can use the resource quota.

    • Resource usage roles: Allow only specific roles to use this resource quota.

    • Resource usage quota: Limit the maximum number of GPU cards, CPU cores, and memory that different roles can use when submitting tasks within a specified priority range.

      Important

      If a user matches multiple constraints, the strictest one applies. For example, in a given resource quota, user A matches both an administrator constraint (priority 1–7, up to 100 GPUs) and a member A constraint (priority 7–9, up to 10 GPUs). When user A submits a priority 7 task under this quota, the maximum allowed is 10 GPUs.

    • Resource specification template: For resource quotas with a resource specification template configured, users must select a template when creating a DSW instance or DLC job.

    DLC

    • Maximum runtime: Set the maximum runtime for a job. The system automatically stops the job if it exceeds this limit.

    • Task priority: Restrict the highest priority that different roles or members can assign when submitting jobs.

    • Allow use of public resources: When disabled, you cannot create pay-as-you-go DLC jobs in the current workspace, preventing unexpected costs.

    • Maximum job wait time: Set timeout thresholds for job waiting time, queuing time, and environment preparation time under a resource quota. The system sends a notification if any threshold is exceeded.

      Note

      To receive timeout alerts, you must also configure notification rules for DLC jobs on the Event notification configuration page. Otherwise, setting timeouts here alone will not trigger alerts.

    DSW

    • Auto shutdown policy:

      • Shutdown policy: Automatically shut down instances based on runtime or resource usage metrics (such as idle duration or CPU, memory, or GPU utilization) to reduce costs.

      • Exclusion policy: Prevent critical DSW instances from automatic shutdown by specifying instance priority and instance name.

    • Instance priority: Restrict the highest priority that different roles or members can assign when creating instances.

    • Allow use of public resources: When disabled, you cannot create pay-as-you-go DSW instances in the current workspace, preventing unexpected costs.

    • Maximum instance wait time: Define timeout rules for resource quota usage. Stop the instance if queuing time or environment preparation time exceeds the threshold.