@@ -125,6 +125,8 @@ are stored in ``$spack/var/spack/cache``. These are stored indefinitely
125125by default. Can be purged with :ref: `spack clean --downloads
126126<cmd-spack-clean>`.
127127
128+ .. _Misc Cache :
129+
128130--------------------
129131``misc_cache ``
130132--------------------
@@ -334,3 +336,52 @@ create a new alias called ``inst`` that will always call ``install -v``:
334336
335337 aliases :
336338 inst : install -v
339+
340+ -------------------------------
341+ ``concretization_cache:enable ``
342+ -------------------------------
343+
344+ When set to ``true ``, Spack will utilize a cache of solver outputs from
345+ successful concretization runs. When enabled, Spack will check the concretization
346+ cache prior to running the solver. If a previous request to solve a given
347+ problem is present in the cache, Spack will load the concrete specs and other
348+ solver data from the cache rather than running the solver. Specs not previously
349+ concretized will be added to the cache on a successful solve. The cache additionally
350+ holds solver statistics, so commands like ``spack solve `` will still return information
351+ about the run that produced a given solver result.
352+
353+ This cache is a subcache of the :ref: `Misc Cache ` and as such will be cleaned when the Misc
354+ Cache is cleaned.
355+
356+ When ``false `` or ommitted, all concretization requests will be performed from scatch
357+
358+ ----------------------------
359+ ``concretization_cache:url ``
360+ ----------------------------
361+
362+ Path to the location where Spack will root the concretization cache. Currently this only supports
363+ paths on the local filesystem.
364+
365+ Default location is under the :ref: `Misc Cache ` at: ``$misc_cache/concretization ``
366+
367+ ------------------------------------
368+ ``concretization_cache:entry_limit ``
369+ ------------------------------------
370+
371+ Sets a limit on the number of concretization results that Spack will cache. The limit is evaluated
372+ after each concretization run; if Spack has stored more results than the limit allows, the
373+ oldest concretization results are pruned until 10% of the limit has been removed.
374+
375+ Setting this value to 0 disables the automatic pruning. It is expected users will be
376+ responsible for maintaining this cache.
377+
378+ -----------------------------------
379+ ``concretization_cache:size_limit ``
380+ -----------------------------------
381+
382+ Sets a limit on the size of the concretization cache in bytes. The limit is evaluated
383+ after each concretization run; if Spack has stored more results than the limit allows, the
384+ oldest concretization results are pruned until 10% of the limit has been removed.
385+
386+ Setting this value to 0 disables the automatic pruning. It is expected users will be
387+ responsible for maintaining this cache.
0 commit comments