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:39] – [CMS Prefetch Configuration] twn | 72:cms_prefetch [2020/10/21 12:46] – [CMS Prefetch Configuration] twn | ||
---|---|---|---|
Line 25: | Line 25: | ||
</ | </ | ||
- | A more detailed description of these properties can be found in the following | + | A more detailed description of these properties can be found in the following |
- | |==== Property ==== | + | |
- | + | | |
- | |==== Description ==== | + | |
- | + | * **cms.cache.refreshIntervalInMinutes** | |
- | | | + | |
- | | \\ | + | |
- | cms.prefetch.activated| \\ | + | * **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. |
- | \\ | + | |
- | Default: true| | + | * **cms.prefetch.workersCount** |
- | | \\ | + | |
- | cms.cache.refreshIntervalInMinutes| \\ | + | |
- | | + | * **cms.prefetch.strategy.class** |
- | \\ | + | |
- | Default: 60| | + | |
- | | \\ | + | * **cms.prefetch.maxParallelTasks.< |
- | cms.prefetch.sleepMillisBetweenDocuments| \\ | + | |
- | | + | |
- | \\ | + | |
- | Default: 0| | + | |
- | | \\ | + | |
- | cms.prefetch.workersCount| \\ | + | |
- | | + | |
- | \\ | + | |
- | Default: 1| | + | |
- | | \\ | + | |
- | cms.prefetch.strategy.class| \\ | + | |
- | | + | |
- | \\ | + | |
- | 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** |
- | | \\ | + | * ****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. |
- | | + | |
- | | + | |
- | \\ | + | |
- | | + | |
=== Strategies === | === Strategies === | ||
Line 74: | Line 55: | ||
The following prefetch strategies are currently available. | The following prefetch strategies are currently available. | ||
- | //Classic all documents available//< | + | //Classic all documents available// |
+ | < | ||
class=AllDocumentsStrategy | class=AllDocumentsStrategy | ||
Line 83: | Line 65: | ||
//Prefetch by CMS type strategy// | //Prefetch by CMS type strategy// | ||
+ | |||
< | < | ||
class=CMSTypeStrategy | class=CMSTypeStrategy | ||
Line 116: | Line 99: | ||
The cache size has a fixed size but will be configurable from Version 7.4.6.1, 7.5.2.1 and above. | The cache size has a fixed size but will be configurable from Version 7.4.6.1, 7.5.2.1 and above. | ||
- | |||
- | \\ | ||