Resource policies let workspace administrators control how compute resources are allocated and used across PAI modules. With resource policies, you can:
Restrict which modules and roles can access a resource quota
Cap GPU, CPU, and memory consumption per role
Enforce job and instance priorities
Auto-shutdown idle DSW instances to reduce costs
Block pay-as-you-go spending to prevent unexpected charges
Set timeout thresholds for DLC jobs and DSW instances
Non-workspace members are users who submit jobs via RAM (Resource Access Management) permissions but have not been added to the workspace. Resource policies can include separate constraints for these users.
Resource usage
Resource usage settings define which modules and roles can consume a resource quota, and how much they can use. Without configuration, the quota is available to all modules and roles without restriction.
| Setting | Description |
|---|---|
| Resource usage modules | Restricts the quota to specific modules, such as DSW or DLC. |
| Resource usage roles | Restricts the quota to specific roles. |
| Resource usage amount | Sets the maximum GPUs, CPU cores, and memory that different roles can use from this quota when submitting jobs within a given priority range. |
| Resource specification template | If set, users must select this template when creating DSW instances or DLC jobs. |
How multiple constraints interact
When a user is subject to more than one constraint, the strictest constraint applies. For example, if User A is bound by both an administrator constraint (100 GPUs for priorities 1–7) and a Member A constraint (10 GPUs for priorities 7–9), a priority 7 job submitted by User A is limited to 10 GPUs from this quota.
DLC
Configure runtime limits, job priorities, and cost controls for DLC (Distributed Learning Cluster) jobs.
| Setting | Type | Description |
|---|---|---|
| Maximum runtime | Blocking | Sets the maximum time a job can run. Jobs that exceed this limit are automatically stopped. |
| Job priority | Blocking | Sets the maximum priority level that different roles or members can assign when submitting jobs. |
| Allow public resources | Blocking | When disabled, users cannot create pay-as-you-go DLC jobs in this workspace. Disable this setting to prevent unexpected charges. |
| Maximum job wait time | Notification only | Sets the maximum time a job can spend waiting, queuing, or preparing its environment. A notification is sent when the threshold is exceeded. |
To receive Maximum job wait time alerts, configure notification rules for DLC jobs on the Event Notification Configuration page. This setting alone does not send alerts.
DSW
Configure auto-shutdown behavior, instance priorities, and cost controls for DSW instances.
Auto-shutdown policy
Auto-shutdown automatically stops instances to save costs when they are no longer actively used.
| Sub-setting | Description |
|---|---|
| Shutdown policy | Defines when an instance is shut down, based on its total runtime or resource usage — including idle time, CPU utilization, memory utilization, and GPU utilization. |
| Exclusion policy | Identifies DSW instances to exempt from auto-shutdown, based on their priority and name. |
Other DSW settings
| Setting | Type | Description |
|---|---|---|
| Instance priority | Blocking | Sets the maximum priority level that different roles or members can assign when creating instances. |
| Allow public resources | Blocking | When disabled, users cannot create pay-as-you-go DSW instances in this workspace. Disable this setting to prevent unexpected charges. |
| Maximum instance wait time | Blocking | Sets the maximum time an instance can spend queuing or preparing its environment. Instances that exceed this threshold are stopped automatically. |
