Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| 74:cms_prefetch [2020/08/25 07:58] – tssr | 74:cms_prefetch [2020/08/25 13:18] – tssr | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | [[: | ||
| + | |||
| ====== CMS Prefetch Configuration ====== | ====== CMS Prefetch Configuration ====== | ||
| Line 6: | Line 8: | ||
| === Configuration of the CMS Prefetch === | === Configuration of the CMS Prefetch === | ||
| - | The default configuration of the CMS prefetch is found in <font inherit/ | + | The default configuration of the CMS prefetch is found in <font inherit/ |
| - | < | + | < |
| - | < | + | < |
| - | < | + | |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | value=" | + | |
| - | </ | + | </ |
| - | <cms> ... </ | + | < |
| </ | </ | ||
| Line 34: | Line 35: | ||
| //Classic all documents available// | //Classic all documents available// | ||
| < | < | ||
| - | \\ | ||
| class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy | class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy | ||
| Line 43: | Line 43: | ||
| //Prefetch by CMS type strategy// | //Prefetch by CMS type strategy// | ||
| < | < | ||
| - | \\ | ||
| class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy | class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy | ||
| Line 53: | Line 52: | ||
| < | < | ||
| - | \\ | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | |
| - | value=" | + | < |
| - | < | + | < |
| - | <!--0 is mapped to unlimited, if nothing were configured it would\\ | + | |
| - | default to 1 --> | + | |
| - | < | + | < |
| - | </ | + | </ |
| - | <cms> ... </ | + | <cms> ... </ |
| </ | </ | ||
| </ | </ | ||
| - | === Cache Persistence === | + | ==== Cache Persistence |
| Stages caches two different levels of information regarding files in external configuration management systems. It collects infomation about the folder structure of a CMS and the files contained within these folders. This information is then used for displaying document information such as the version or state of a file. | Stages caches two different levels of information regarding files in external configuration management systems. It collects infomation about the folder structure of a CMS and the files contained within these folders. This information is then used for displaying document information such as the version or state of a file. | ||
| Line 77: | Line 75: | ||
| These caches are persisted in the file system on the application server that runs Stages. | These caches are persisted in the file system on the application server that runs Stages. | ||
| - | **Since 7.4.6.1**: | + | ✘ **Since 7.4.6.1**: |
| + | |||
| + | The properties | ||
| - | The property | + | * // |
| + | * // | ||
| + | can be used to set the maximum amount of objects, which should be cached in memory for the documents-cache and the repository-cache. | ||
| - | The default values are **4096** documents and **20** repositories. | + | The default values are **4096** |