How to Configure the FPC Warmer Extension?

How to Configure the FPC Warmer Extension?

To ensure the FPC Warmer extension automatically warms pages on your website, you need to set up a valid warming schedule. Follow these steps for proper configuration:

      1. Set the Queue Max Size

First, estimate how many pages should be warmed based on your selected Source Type and specify the Queue Max Size option. The extension will take as many links as available. If unsure of the number of links, set a higher number (e.g. 10,000). If there are fewer links, only the available amount will be added to the queue.



      2. Configure Queue Generation Schedule

Next, specify when the queue should be generated using the Queue Generation option. Please note, if a new queue is generated before the previous one is fully processed, unprocessed links will be removed, and warming will start from the beginning. To ensure smooth warming, you may follow this formula: Queue Generation Schedule = (Queue Max Size / Single Batch Size) × Warmer Schedule Interval. For example, there are 2,000 links to warm and the batch size is 50 (processed every 5 minutes), Total Queue processing time equals to 200 minutes (~3.3 hours). Therefore, the Queue Generation Schedule should be no quicker than every 4 hours or * */4 * * *.

To generate a valid Cron expression, kindly use a tool like Crontab guru - cron schedule expression generator.


      
      3. Set Up Batch Processing

      The queue is processed in batches, where each batch contains a fixed number of links (set in "Single Batch Size"). These batches run according to the Warmer Schedule.


      
The ideal Warmer Schedule and Single Batch Size depend on each other, the Page Combinations setting and whether Multi-Process Warming is enabled. To adjust these options for best performance, follow the next steps:

      1. Check Amasty > Cron Schedule List > Cron Tasks List (included with FPC Warmer).
      2. Monitor if batches are processed on time or if jobs are missed by filtering the grid by Job Code = amasty_fpc_process_queue
      

      3. If batches aren’t completed in time: decrease batch size or increase Warmer Schedule interval.
      4. Multi-Process Warming speeds up batch processing by warming multiple links simultaneously. However, it increases the server load - use with caution on high-traffic sites. We recommend running the test warming while monitoring the server load first.