Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| 72:cms_prefetch [2020/10/21 12:36] – [CMS Prefetch Configuration] twn | 72:cms_prefetch [2020/10/21 12:39] – [CMS Prefetch Configuration] twn | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| 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 | + | |
| - | | | + | |
| - | | \\ cms.prefetch.activated \\ | + | |
| - | | \\ In case no configuration management system is configured the prefetch service can be completely deactivated. \\ | + | |
| - | \\ Default: true \\ | + | |==== Description ==== |
| - | | | + | |
| - | | \\ 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) \\ | + | |
| - | \\ Default: 60 \\ | ||
| | | | | ||
| - | | \\ 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. \\ | + | cms.prefetch.activated| |
| - | + | In case no configuration management system is configured the prefetch service can be completely deactivated. \\ | |
| - | \\ Default: 0 \\ | + | \\ |
| - | | | + | |
| - | | \\ cms.prefetch.workersCount | + | | \\ |
| - | | \\ In case the prefetch does not finish its work within the specified referesh interval, the amount of worker threads utilized by the prefetch can be increased. This will lead to additional CPU load and load on the CMS. \\ | + | |
| - | + | 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) \\ | |
| - | \\ Default: 1 \\ | + | \\ |
| - | | | + | |
| - | | \\ cms.prefetch.strategy.class | + | | \\ |
| - | | \\ Specifies the strategy implementation to use to update the document revision information. \\ | + | |
| - | + | 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. \\ | |
| - | \\ Default: AllDocumentsStrategy | + | \\ |
| - | | | + | Default: 0| |
| - | | \\ cms.prefetch.maxParallelTasks.< | + | | \\ |
| - | | \\ Where < | + | cms.prefetch.workersCount| \\ |
| + | In case the prefetch does not finish its work within the specified referesh interval, the amount of worker threads utilized by the prefetch can be increased. This will lead to additional CPU load and load on the CMS. \\ | ||
| + | \\ | ||
| + | Default: 1| | ||
| + | | \\ | ||
| + | cms.prefetch.strategy.class| \\ | ||
| + | Specifies the strategy implementation to use to update the document revision information. \\ | ||
| + | \\ | ||
| + | Default: AllDocumentsStrategy| | ||
| + | | \\ | ||
| + | cms.prefetch.maxParallelTasks.< | ||
| + | | ||
| CMS types specified by the cms-type Tag in the cms Section of config.xml. It will only be \\ | CMS types specified by the cms-type Tag in the cms Section of config.xml. It will only be \\ | ||
| used by some of the available Strategies. E.g. CMSTypeStrategy. It can be used to restrict the amount of parallel tasks that work on the same type of CMS. \\ | used by some of the available Strategies. E.g. CMSTypeStrategy. It can be used to restrict the amount of parallel tasks that work on the same type of CMS. \\ | ||
| - | + | | |
| - | | + | Default: 1| |
| - | | | + | | \\ |
| - | | \\ cms.prefetch.initialStart.hourOfDay \\ | + | cms.prefetch.initialStart.hourOfDay| \\ |
| - | | \\ In case this property exists in config.xml, scheduling of the initial prefetch run will be delayed until the configured hour of the day. Valid values are (0-23). E.g. for 22 the first prefetch run will be delayed to 22:00. It has to be ensured that the Stages service is up and running at this timepoint. If this property does not exist the prefetch will start directly after starting the Stages service. \\ | + | |
| - | + | \\ | |
| - | \\ Default: <not set; start immediatly> | + | Default: <not set; start immediatly> |
| - | | | + | |
| === Strategies === | === Strategies === | ||