Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
72:cms_prefetch [2018/10/08 13:38] – etea | 72:cms_prefetch [2020/08/25 07:29] – tssr | ||
---|---|---|---|
Line 8: | 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/ |
- | < | ||
< | < | ||
< | < | ||
Line 23: | Line 22: | ||
< | < | ||
</ | </ | ||
+ | |||
</ | </ | ||
Line 36: | Line 36: | ||
< | < | ||
class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy | class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy | ||
+ | |||
</ | </ | ||
Line 43: | Line 44: | ||
< | < | ||
class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy | class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy | ||
+ | |||
</ | </ | ||
Line 64: | Line 66: | ||
< | < | ||
</ | </ | ||
+ | |||
</ | </ | ||
Line 70: | Line 73: | ||
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. | ||
- | These caches are - by default - persisted in the file system on the application server that runs Stages. However the administrator may configure these caches to be stored within a relational Database. This increases cache performance significantly. | + | These caches are persisted in the file system on the application server that runs Stages. |
- | The configuration | + | To optimize the usage of memory on the application server, the administrator can configure the cache size. |
- | Each cache requires its own configuration | + | **In Version VERSION |
- | //Note//: After changing the cache persistence settings, the Stages configuration has to be updated (''< | + | The property "cms.prefetch.memorycache.max.documents" |
+ | **Since Version**: | ||
+ | For a more accurate adjustment, the cache size can now be configured in MB. The corresponding properties are | ||
+ | " |