ASCEND_CACHE_PATH
Description
If you want the files generated during component build and runtime to be flushed to a unified directory, you can set this environment variable to specify the storage path of shared files.
- The path name can contain letters, digits, underscores (_), hyphens (-), and periods (.).
- Ensure that the specified path exists and is valid. The execution user must have the read, write, and execute permissions on the path.
The following table lists the files in ${ASCEND_CACHE_PATH}.
|
Flushed File |
File Content |
Priority Specification |
|---|---|---|
|
${ASCEND_CACHE_PATH}/aoe_data |
AOE tuning repository file, which can be shared by multiple servers. |
TUNE_BANK_PATH > ASCEND_CACHE_PATH> Default knowledge base path For details about the default knowledge base path, see "Note" in TUNE_BANK_PATH. |
|
${ASCEND_CACHE_PATH}/kernel_cache |
Operator build cache file, which can be shared by multiple devices on a server. |
The following scenarios provide parameters or APIs for setting the storage path of operator compilation cache files. Their priority is higher than that of the ASCEND_CACHE_PATH environment variable. The details are as follows:
|
Example
export ASCEND_CACHE_PATH=/repo/task001/cache
Restrictions
- File locking in Linux needs to be supported by the shared storage (such as NFSv4, OceanStor Pacific 9950, and OceanStor Pacific 9550). But if the storage, such as NFSv3, does not support file locking, you are advised to store files to local directories.
- In the multi-server scenario, the AI processor model, firmware, driver, and CANN software version on each server must be the same.