Below, we compare two very important tools that represent vital performance improvements: Amasty Full Page Cache Warmer and Mirasvit Full Page Cache Warmer. Both crawl your store and warm cache automatically. Which extension is better? Which Magento 2 cache warmer provides more advanced functionality? Which solution is more budget-friendly? You will find answers to these and other questions below.
Let’s start our comparison with one key aspect the nature of the workflow each Magento 2 FPC warmer module provides. Both Amasty and Mirasvit provide fully automated workflow. You only need to configure the extensions and they will do all the work without any manual actions. At the same time the Amasty Full Page Cache Magento 2 warmer provides the ability to force manual queue generation and manual warming.
Since we’ve started the comparison with the description of the automated workflow, it is necessary to mention that both Magento 2 warmer extensions support cron. Thus, you can create any custom schedule for both tools. Note that the Amasty Full Page Cache Warmer Magento 2 extension allows to use the cron expression to schedule queue generation jobs and to use another one to schedule warmer jobs.
In its turn Mirasvit Full Page Cache Warmer provides only one field for the cron expression, where you can schedule warmer jobs.
Warm Pages By
Mirasvit and Amasty allow you to select one of two generation sources. In case of Amasty, it is Page types and Text File.
Mirasvit also allows to specify certain page types to warm your Magento 2 store and at the same time provides the ability to run the process on the basis of page popularity, which is a quite handy option.
Both extensions allow to exclude certain pages from warming.
Performance Improvements and Various Limitations
Another important aspect that has different implementation in the compared modules is related to performance improvements and various limitations. While Amasty allows to set a limit on queue and batch sizes, specify delay between requests, and set the maximum number of lines in the log table:
Mirasvit provides the ability to specify the number of concurrent requests to store, set delay between requests, and specify the maximum job run time:
Besides, there is a group of extended settings:
- Don’t verify peer
- Don’t run warmer job if average system load more than (%)
- Crawler limit
- Forbid cache flushing
Use all these parameters to achieve the maximum effectiveness of the chosen Magento cache warmer.
To make the warming workflow more precise, the Amasty Full Page Cache Warmer Magento 2 extension allows to create page combinations on the basis of sore views, customer groups, and currencies.
Mirasvit doesn’t provide any similar functionality.
Both extensions allow to configure the debug mode. Amasty Magento 2 warmer allows to display cache status or specify IP addresses to show it for.
Mirasvit offers two additional parameters: Log tags for cache flushing and Log backtrace for cache flushing.
In case of the Amasty FPC Warmer Magento 2 module the warmer queue is available in a grid that displays only page URL and rate.
As for the Mirasvit Magento 2 crawler, it offers a more informative page ID, URL, type, and popularity. You can warm or clear cache as well as delete each page individually from the Action column. Besides, there is a section that illustrates the percent of cached and pending pages as well as shows fill rate.
The Amasty Full Page Cache Wormer Magento 2 module contains a log where all warmed pages are gathered. Here, you can view date when the page was warmed, its URL, related store view/currency/customer group, rate, status, and execution time.
In its turn Mirasvit warmer displays both completed and running jobs together. You can view job ID, info (fill rate, average system load, and execution time), status (running or completed), as well as time and date of creation/start/finish.
The Reports page of Mirasvit’s module looks more user-friendly and informative. It contains only one diagram, but you can add up to 6 parameters to it and display data for various time intervals: Hour of day, Day, Week, Month, or Year. As for parameters, they are: Average Response Time, Hit Average Response Time, Miss Average Response Time, Hit Count, Miss Count, and Visit Count.
Besides, there is a grid view below the diagram.
In case of Amasty, you have two diagrams: Status Codes and Warmed Pages. Neither of them provides such a wide variety of settings, and you don’t get a grid view.
On the frontend, both Magento 2 warmer extensions have the same functionality. They display cache hit and cache miss as well as not cacheable blocks.
As for the price of both modules, it is almost the same. You can purchase Amasty Full Page Cache Magento 2 extension for $175, while its competitor costs $149. Thus, Mirasvit offers a slightly more budget friendly tool.
Magento 2 FPC Warmers Comparison
|Several Warm Types||+||+|
As you can see, each module has its pros and cons. If you are looking for the cheapest solutions – choose Mirasvit. If detailed reports are important – purchase the same module. If lots of settings are your key requirement, you already know the answer.
In its turn the Amasty Full Page Cache Warmer Magento 2 module is greate since it offers manual mass update in addition to the fully automated algorythm as well as allows to leverage customer groups, store views, and currencies to make page warming more precise. We also recommend you to use Amasty if you already use company’s modules, since you will avoid conflicts for sure. The same is about Mirasvit