ASCEND_CACHE_PATH
Description
- The path specified by this environment variable can contain only uppercase letters, lowercase 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.
The following table lists the files flushed by each component to ${ASCEND_CACHE_PATH}.
|
Component |
Path |
File Content |
Priority Specification |
|---|---|---|---|
|
AOE |
${ASCEND_CACHE_PATH}/aoe_data |
Repository file, which can be shared by multiple servers. |
TUNE_BANK_PATH > ASCEND_CACHE_PATH> Default repository path For details about the default repository path, see "Note" in TUNE_BANK_PATH. |
|
ATC |
${ASCEND_CACHE_PATH}/kernel_cache |
Operator build cache file, which can be shared by multiple devices on a server. |
Parameter --op_compiler_cache_dir > ASCEND_CACHE_PATH > Default path ($HOME/atc_data) |
|
TF Adapter |
${ASCEND_CACHE_PATH}/kernel_cache |
Operator build cache file, which can be shared by multiple devices on a server. |
TF Adapter configuration parameter op_compiler_cache_dir > ASCEND_CACHE_PATH > Default path ($HOME/atc_data) |
|
AscendCL |
${ASCEND_CACHE_PATH}/kernel_cache |
Operator build cache file, which can be shared by multiple devices on a server. |
|
Example
export ASCEND_CACHE_PATH=/repo/task001/cache
Restrictions
- File locking in Linux needs to be supported by the shared storage (such as NFSv4 and OceanStor Pacific 9950 and 9550). But if the storage, such as NFSv3, does not support file locking, you are advised storing 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.