Create a DSW instance with idle resources
When creating a DSW instance with a subscription resource quota, you can enable idle resources to borrow idle compute from other quotas. This reduces resource costs without affecting normal workloads.
Background
In the PAI platform, you can divide and assign quotas based on your business needs. Each team's DSW instances consume compute from their own quota. However, some teams may have idle quota capacity during certain periods while others queue up due to insufficient quota — resulting in resource imbalances and waste.
DSW's idle resources feature addresses this. When creating a DSW instance, enabling idle resources lets the instance borrow idle compute from other quotas without disrupting normal workloads, improving overall resource utilization and reducing costs.
How it works:
DSW instances using a dedicated general-purpose compute resource quota can borrow idle compute within the same quota. DSW instances using a Lingjun Computing resource quota can borrow idle compute of the same resource type across all quotas in the tenant.
DSW instances running on idle resources use idle compute from the current or other quotas without counting against their own quota limits.
DSW instances using idle resources are automatically terminated when the original quota's tasks need the resources back, and the capacity is returned to the quota.
DSW instances running on idle resources may be interrupted due to resource reclamation. Save your environment and data regularly.
Prerequisites
A subscription resource quota (dedicated general-purpose compute or Lingjun Computing resource quota) has been created and bound to a workspace. For details, see Overview.
Create a DSW instance with idle resources
Follow these steps to configure and enable idle resources when creating a DSW instance.
Log in to the PAI console.
In the left navigation pane, click Workspaces, then select and enter the target workspace.
In the left navigation pane, click Interactive Modeling (DSW) > Create Instance, and go to the instance creation page.
-
In the Resource information section, set Resource Type to Resource Quota, then configure the Idle Resources parameter:
Acceptable: The instance can use idle compute from the current 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 other parameters such as instance name, resource type, and image, then click OK to create the instance. For descriptions of other parameters, see Create a DSW instance.
Best practices
Save environment and data regularly: Idle resources can be reclaimed at any time. Store important code and data in persistent storage such as OSS or NAS to avoid data loss when an instance is terminated. For details, see Mount a dataset, OSS, NAS, or CPFS.
Use for non-critical tasks: Idle resources are well-suited for experimentation, debugging, and data exploration where brief interruptions are acceptable. For tasks that must run continuously, use standard quota resources instead.
Save custom images: Periodically save your development environment as a custom image so that you can restore the environment after an instance is reclaimed. For details, see Create a DSW instance image.