Skip to content

Commit 7fc2c9b

Browse files
authored
Merge branch 'main' into mgs28-char-rnn-update
2 parents cac1c3e + 1263f06 commit 7fc2c9b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

recipes_source/torch_compile_caching_tutorial.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Before starting this recipe, make sure that you have the following:
2323
Inductor Cache Settings
2424
----------------------------
2525

26-
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.
26+
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.
2727

2828
There are a few settings relevant to caching and to FX graph caching in particular.
2929
The settings are accessible via environment variables listed below or can be hard-coded in Inductor’s config file.

0 commit comments

Comments
 (0)