Page Cache Warmer settings

The settings of Cache Warmer are located at System ▸ Page Cache Warmer ▸ Settings and grouped into the following sections:

  • General Settings - basic configuration of warming process.
  • Performance - allows you to manage performance of Cache Warmer.
  • Extended Settings - advanced settings to fine-tune server load and improve its responsiveness.
  • FPC hole punch - settings for excluding individual blocks from caching.
  • Debug - provides you with additional debug information about cache.

General Settings

  • Enabled - enables/disables Page Cache Warmer.
  • Ignored Pages - allows to set URL patterns for pages that should be ignored by Cache Warmer. Consists of records, where Expression contains regular expression for URL.

    Example

    • /\?/ - ignore all pages, that have GET params (filtered category pages, search results pages, etc.)
    • /\?[\w=]*&[\w=]*&[\w=]*/ - ignore pages with more than 2 GET params

    Read more about regular expression.

  • Ignored User-agents - allows to set patterns of user-agent headers, which will be ignored by cache warmer. For example, you can set /.*Googlebot.*/ to ignore Google crawler. And pages visited by Google crawler will not be added to the queue of cache warmer.

Performance

This section will help you to tune-up Page Cache Warmer crawler. The crawler is launched regularly based on cron schedule and begins to traverse the list of available URLs of the store:

  • If URL is already cached, it is skipped;
  • If URL is not in the cache, crawler will visit it on behalf of external user so that the page is rendered and placed in the cache.

To adjust the performance of crawler you can use the following options:

  • Threads - the number of concurrent (parallel) requests to the store.
  • Delay between requests - delay between requests in milliseconds.
  • Maximum job run time - maximum running time allowed for crawler job in seconds.
  • Job Schedule - Cron expression for schedule warmer jobs. Read more about setting Cron expressions here.

Extended Settings

  • Don't run warmer job if average system load more than (%) - If average system load exceeds value in this field, warmer job will not start. Average system load graph can be seen at SYSTEM->Page Cache Warmer -> Jobs. Read more in this FAQ section.
  • Crawler limit - Crawler will stop crawling when quantity of URLs in cache reaches this value.
  • Forbid cache flushing - completely disables flushing FPC cache. Read more in this FAQ section.
  • Run warmer as web server user - Enable this option only if cron user does not have enough permissions to warm pages.
  • Forcibly make pages cacheable - Allows to override default behavior of Magento with regard to caching pages by changing content block attributes:

    • Disable - keeps Magento's default caching behavior.
    • All pages - extension will delete cacheable="false" for all blocks in home, category and product pages making them cacheable as a result.
    • Configure - allows to select page types which will be made cacheable, eg. Home page (Cms · Index · Index), category (Catalog · Category · View) and product pages (Catalog · Product · View) make_pages_cacheable_by_page_type.png
  • Warm mobile pages separately - Enable only if you want your store to create different cached pages for mobile and desktop users.
  • Use the same cache for new visitor - Allows to avoid creation of several copies of cached pages for Magento installations with multiple storeviews. Disable it in case if your pages for different languages/currencies/storeviews are cached incorrectly.

Debug

  • Show cache status - show block in the store frontend with page cache status.
  • Hole punch info - show hint for 'hole punched' blocks. Read more in FPC hole punch section.
  • Show cache status and hole punch info only for - сomma separated IP addresses, for which info box should be visible.
  • Log tags for cache flushing - logs all cache flushes to /var/log/clean.log file.
  • Log backtrace for cache flushing - logs backtrace for cache flushes to the /var/log/clean.log. For more info on this and previous setting, read more in this FAQ section.