What Are the Size Limits of the /cache Directories for Resources with Varying Specifications on ModelArts Notebook Instances?

When creating a notebook instance, you can select resources based on the data volume. ModelArts mounts disks to /cache. You can use this directory to store temporary files. The /cache directory shares resources with the code directory. The directory size varies depending on resource specifications.

Do not store important data on the /cache disk. Exceptions such as container breakdown, node faults, and insufficient resources (for example, the memory or storage exceeds the limit) may cause instance restart, resulting in data loss on the /cache disk.

• Old resource pool: Local disks are used. To obtain the upper limit size of the /cache directory, see Table 1. The mapping format is as follows:
  • Currently, the /cache directory cannot be configured for CPUs.
  • If you use a single GP or Ascend processor, the /cache directory size is limited to 500 GB.
  • If you use more than one processing unit (PU), the /cache directory size limit depends on the number of PUs. The size limit is the number of PUs times 500 GB, with a maximum of 3 TB.
• New resource pool: A cluster is created and EVS disk mounting is enabled. When you create a dedicated resource pool, the set disk capacity is the total available for allocation. Each PU gets a share of this disk space based on the total number of PUs in the pool.

  The /cache directory size limit for an instance is calculated as: Number of PUs used by the instance × /Cache directory size per PU.