When creating a DSW instance with a subscription resource quota, you can enable idle resource usage to access idle compute from other quotas and lower costs.
Background
PAI lets you divide and assign quotas based on your business needs. DSW instances from different teams each consume their own quota. However, some quotas may sit idle during certain periods while others experience queuing due to insufficient resources, leading to resource underutilization and waste.
To address this, DSW provides idle resource usage. When you create a DSW instance with idle resource enabled, the instance can draw on idle compute from other quotas without affecting normal workloads. This improves overall resource utilization and lowers costs.
How it works:
A DSW instance using idle resources can access idle compute from the current quota or other quotas, bypassing the total and remaining capacity limits of its own quota.
When the original quota's workloads need those resources back, the DSW instance is terminated and the resources are automatically reclaimed.
DSW instances running on idle resources may be interrupted at any time. Save your environment and data regularly.
Prerequisites
A subscription resource quota (including dedicated general-purpose compute resource quotas and Lingjun intelligent computing resource quotas) created and bound to a workspace. For details, see Overview.
Create a DSW instance with idle resources
Log on to the PAI console.
In the left navigation pane, click Workspaces, then select the target workspace.
In the left navigation pane, click Interactive Modeling (DSW) > Create Instance. The Create DSW Instance page appears.
-
In the Resource information section, set Resource Type to Resource Quota, then configure Idle Resources:
Acceptable: The instance can use idle compute from the current quota or other quotas in the account.
Only Acceptable: The instance uses only idle resources in the account and doesn't consume its own quota.
Configure the remaining parameters (such as instance name, resource type, and image), then click OK to create the instance. For details on the other parameters, see Create a DSW instance.
Best practices
Save your environment and data regularly: Idle resources can be reclaimed at any time. Store important code and data in persistent storage such as Object Storage Service (OSS) or Apsara File Storage NAS to prevent data loss when an instance is interrupted. For details, see Mount a dataset, OSS, NAS, or CPFS.
Use for non-critical workloads: Idle resources are well suited for interruption-tolerant workloads, such as experiments, debugging, and data exploration. For critical workloads that need to run continuously, use a dedicated quota.
Save custom images: Regularly save your development environment as a custom image so you can restore it quickly after an instance is reclaimed. For details, see Create a DSW instance image.