v4.3.3 update. (#2868)
This commit is contained in:
@@ -128,7 +128,7 @@ Here is an example demonstrating automatic caching of the ``add`` kernel:
|
||||
The cache can be serialized to files for subsequent runs.
|
||||
After serialization, compiled MLIR bytecode is stored in file.
|
||||
The cache directory is ``/tmp/{current_user}/cutlass_python_cache``.
|
||||
The cache loads from files into memory during |DSL| initialization and saves back to files when the process exits.
|
||||
During compilation, the cache loads the corresponding kernel from file (if it exists) into memory as needed, and after compilation, it saves any newly compiled executables back to file.
|
||||
|
||||
Note that for efficiency, the default cache directory is located in a temporary folder. However, this location is not persistent, it may be cleared by the system (for example, during a reboot or disk space cleanup).
|
||||
If you wish to preserve the cache across sessions, set the ``CUTE_DSL_CACHE_DIR`` environment variable to point to a persistent directory.
|
||||
@@ -140,9 +140,6 @@ The following environment variables control file caching:
|
||||
# Disable file caching while keeping in-memory cache available, defaults to False.
|
||||
export CUTE_DSL_DISABLE_FILE_CACHING=True
|
||||
|
||||
# Maximum number of cache files allowed, defaults to 1000.
|
||||
export CUTE_DSL_FILE_CACHING_CAPACITY=1000
|
||||
|
||||
# Cache directory, defaults to /tmp/{current_user}/cutlass_python_cache.
|
||||
export CUTE_DSL_CACHE_DIR=/home/user/local_cutlass_python_cache/dense_gemm_cache/
|
||||
|
||||
|
||||
Reference in New Issue
Block a user