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/07/17 13:20] – [CMS Prefetch Configuration] bkkr | 72:cms_prefetch [2020/08/25 07:53] – [CMS Prefetch Configuration] tssr | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Configure the Stages Server | + | [[: |
====== CMS Prefetch Configuration ====== | ====== CMS Prefetch Configuration ====== | ||
Line 8: | Line 8: | ||
=== Configuration of the CMS Prefetch === | === Configuration of the CMS Prefetch === | ||
- | The default configuration of the CMS prefetch is found in '' | + | The default configuration of the CMS prefetch is found in <font inherit/ |
- | <code> | + | <stages-config> |
- | <pkit-config> | + | |
< | < | ||
Line 22: | Line 21: | ||
</ | </ | ||
< | < | ||
- | </pkit-config> | + | </stages-config> |
</ | </ | ||
A more detailed description of these properties can be found in the following table: | A more detailed description of these properties can be found in the following table: | ||
- | ^Property^Description| | + | TBD |
- | |cms.prefetch.activated| | + | |
- | In case no configuration management system is configured the prefetch | + | === Strategies === |
- | \\ | + | |
- | Default = true| | + | The following |
- | |cms.cache.refreshIntervalInMinutes| | + | |
- | A new prefetch run will be started after this period of time. (In case of a too short interval it will be delayed until the previous run has finished) \\ | + | //Classic all documents available// |
- | \\ | + | < |
- | | + | class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy |
- | |cms.cache. lastAccessIntervalForActiveProjectsInDays| | + | |
- | The prefetch will only update | + | </ |
- | \\ | + | |
- | Default = 4| | + | This strategy ignores the maxParallelTasks properties. (cms.prefetch.maxParallelTasks.< |
- | |cms.prefetch.sleepMillisBetweenDocuments| | + | |
- | In case the prefetch service produces too much CPU load on the Stages server or on the CMS, it can be forced to pause for some time. This will of course lead to longer running prefetches. \\ | + | //Prefetch by CMS type strategy// |
- | \\ | + | < |
- | Default = 0| | + | class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy |
- | |cms.prefetch.workersCount| | + | |
- | In case the prefetch does not finish its work within the specified referesh interval, | + | </ |
- | \\ | + | |
- | Default | + | This strategy allows more detailed configuration |
- | |cms.prefetch.strategy.class| \\ | + | |
- | Specifies the strategy implementation to use to update the document revision information. \\ | + | cms.prefetch.maxParallelTasks. allows to specify |
- | \\ | + | |
- | | + | < |
- | |cms.prefetch.maxParallelTasks.<CMSType>| \\ | + | < |
- | Where <CMSType> | + | < |
- | \\ | + | < |
- | Default = 1| | + | < |
- | |cms.prefetch.initialStart.hourOfDay| | + | value=" |
- | In case this property exists in PKitConfig.xml, | + | < |
- | \\ | + | <!--0 is mapped to unlimited, if nothing were configured it would |
- | Default: | + | |
- | | | + | |
+ | < | ||
+ | </ | ||
+ | |||
+ | <cms> ... </ | ||
+ | </stages-config> | ||
+ | |||
+ | </code> | ||
+ | |||
+ | === 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. |
+ | 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 7.4.6.1, 7.5.2.1 and above. |