Build up your caches for your Craft site with a cache warmer.
The warmer will look at your sites(s) sitemap.xml and visit them, building up the caches (image transforms, imager, html etc) and making the site load faster for your user. This can be useful when clearing the caches after a release for example, or anytime you clear a site's caches, or make changes in your content.
There are several ways to trigger it, visit the usage page for more documentation.
Some urls can be ignored in the backend's settings, for each site.
The front end and the control panel triggers can benefit from parallel execution, making the process quicker. The amount of processes and the amount of urls one process will warm are editable in settings.
The parallel execution does not work for console or curl requests. The system will try to set your max_execution_time setting (if allowed by your server), and will visit all urls.
A locking system can prevent several instances of the cache warming.
The warmer will tell you which http code returns each of your urls, so you can quickly spot any issues.
It's important that you set your config
true or your assets transforms won't be generated.
You can send an email after each warmer's run.
From 2.1.0 elements urls (and related elements urls) can be warmed automatically when they are saved, this will need to be enabled in the settings.
- Craft 3.5
- If you server doesn't allow max_execution_time to be changed, you will be facing issues on large sites for the command line and curl