Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
72:cms_prefetch [2020/10/21 12:46]
Thomas Weinlein [CMS Prefetch Configuration]
72:cms_prefetch [2020/10/21 12:48] (current)
Thomas Weinlein [CMS Prefetch Configuration]
Line 34: Line 34:
       * Default: 60       * Default: 60
   * **cms.prefetch.sleepMillisBetweenDocuments**   * **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.+      * 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: 0       * Default: 0
   * **cms.prefetch.workersCount**   * **cms.prefetch.workersCount**
Line 43: Line 43:
       * Default: AllDocumentsStrategy       * Default: AllDocumentsStrategy
   * **cms.prefetch.maxParallelTasks.<​CMSType>​**   * **cms.prefetch.maxParallelTasks.<​CMSType>​**
-      * Where <​CMSType>​ is the name of one of the \\ +      * Where <​CMSType>​ is the name of one of the 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.
-   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.+
       * Default: 1       * 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.+      * 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>​