Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 74:cms_prefetch [2020/08/25 07:57] – created tssr | 74:cms_prefetch [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | [[: | ||
| + | |||
| ====== CMS Prefetch Configuration ====== | ====== CMS Prefetch Configuration ====== | ||
| The CMS prefetch is a Stages system service. It ensures that Stages displays up to date information of documents that are managed by an external configuration management system (CMS). Therefore the CMS prefetch is scheduled periodically to retrieve the latest revision information for all documents of active projects. | The CMS prefetch is a Stages system service. It ensures that Stages displays up to date information of documents that are managed by an external configuration management system (CMS). Therefore the CMS prefetch is scheduled periodically to retrieve the latest revision information for all documents of active projects. | ||
| - | //Note//: All changes of the configuration described in this document require a restart of the Stages service.\\ | + | //Note//: All changes of the configuration described in this document require a restart of the Stages service. |
| === 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 ''< |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | value=" | + | |
| - | </ | + | </ |
| - | <cms> ... </ | + | < |
| </ | </ | ||
| - | |||
| </ | </ | ||
| Line 32: | Line 33: | ||
| The following prefetch strategies are currently available. | The following prefetch strategies are currently available. | ||
| - | //Classic all documents available//\\ | + | //Classic all documents available// |
| - | < | + | < |
| class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy | class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy | ||
| - | |||
| </ | </ | ||
| Line 41: | Line 41: | ||
| This strategy ignores the maxParallelTasks properties. (cms.prefetch.maxParallelTasks.< | This strategy ignores the maxParallelTasks properties. (cms.prefetch.maxParallelTasks.< | ||
| - | //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 52: | Line 51: | ||
| cms.prefetch.maxParallelTasks. allows to specify the maximum number of workers that are allowed to process documents of that CMS type. This is useful in case different CMS types are used by one Stages deployment and the CM systems have very different performance characteristics. So it is e.g. possible to specify that there is only one worker for SVN and all other workers should be used for Integrity. This example would need the following configuration: | cms.prefetch.maxParallelTasks. allows to specify the maximum number of workers that are allowed to process documents of that CMS type. This is useful in case different CMS types are used by one Stages deployment and the CM systems have very different performance characteristics. So it is e.g. possible to specify that there is only one worker for SVN and all other workers should be used for Integrity. This example would need the following configuration: | ||
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | < | + | < |
| - | 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. | ||
| - | The cache size has a fixed size but will be configurable from Version | + | ✘ **Since |
| + | |||
| + | The properties | ||
| + | |||
| + | * //cms.prefetch.memorycache.max.documents// | ||
| + | * // | ||
| + | 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** | ||