From 00ad07b29672cfa2c4ccdca8e7ccf0d7feb0f3b9 Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 6 Dec 2024 12:55:39 -0800 Subject: [PATCH] Fix typo in torch_compile_caching_tutorial.rst Follow up on https://github.com/pytorch/tutorials/pull/3177 --- recipes_source/torch_compile_caching_tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes_source/torch_compile_caching_tutorial.rst b/recipes_source/torch_compile_caching_tutorial.rst index 5dc3788b2e1..3c024828f9f 100644 --- a/recipes_source/torch_compile_caching_tutorial.rst +++ b/recipes_source/torch_compile_caching_tutorial.rst @@ -23,7 +23,7 @@ Before starting this recipe, make sure that you have the following: Inductor Cache Settings ---------------------------- -Most of these caches are in-memory, only used within the same process, and are transparent to the user. An exception are caches tha stores compiled FX graphs (FXGraphCache, AOTAutogradCache). These caches allow Inductor to avoid recompilation across process boundaries when it encounters the same graph with the same Tensor input shapes (and the same configuration). The default implementation stores compiled artifacts in the system temp directory. An optional feature also supports sharing those artifacts within a cluster by storing them in a Redis database. +Most of these caches are in-memory, only used within the same process, and are transparent to the user. An exception is caches that store compiled FX graphs (FXGraphCache, AOTAutogradCache). These caches allow Inductor to avoid recompilation across process boundaries when it encounters the same graph with the same Tensor input shapes (and the same configuration). The default implementation stores compiled artifacts in the system temp directory. An optional feature also supports sharing those artifacts within a cluster by storing them in a Redis database. There are a few settings relevant to caching and to FX graph caching in particular. The settings are accessible via environment variables listed below or can be hard-coded in Inductor’s config file.