Full Page Cache

Please navigate to System > Configurations > Amasty Extensions > FPC > Statistics >

Choose "Yes" in the dropdown and then generate a queue in System > Configurations > Amasty Extensions > FPC Crawler > Force cron job actions >

Please follow to System >> Configurations >> Amasty Extensions >> Full Page Cache >> Search Engines. In User Agents option the curl should be removed:

Yes, Magento Full Page Cache allows for hole punch applied to dynamic blocks as well as cart/welcome and CMS blocks. You can exclude the blocks added via the amfpc.xml. Address the user guide to see a step-by-step instruction. 

It is extremely important to keep shopping cart page, customer account and all checkout pages uncached for correct operation of checkout process. That is why Amasty Full Page Cache extension has special settings to control caching of these areas.

Moreover, there is an “Ignore List” setting where you can list all the pages you want to hole punch, including categories, product and CMS pages.

Yes, our Full Page Cache module supports Redis as well as other Magento backend caches: Memcache, APC, File Cache and Database cache. To enable Redis, please follow these steps.

You can see the test results in ms come in the table:

Every test was performed 10 times in order to provide correct calculation of the average value of the test results. This was for 50 simultaneous users jMeter will perform the test scenario 500 times. The test scenario contains 12 requests to the server (download of CSS page resources/JS/images are not taken into account in the test results), this way during the test with 50 simultaneous visitors 6000 requests are sent to the server.

Also, you can pay attention to the page code structure enhancement with the Google Speed Optimization extension.

Redis is one of the most popular caching mechanisms on the web. It keeps data in the server memory (RAM). To set Redis as a cache storage, you need to install and configure it on your server. Please, contact your system administrator or hosting provider for assistance in doing that. When Redis is installed, download pre-configured file or you can find it by its name "z_amfpclocal.xml" in the module folder. Then edit the file by adding Redis data in it and upload the file to app/etc folder. The result is that the database table "core_cache" shouldn't be increased.

We can say from our experience that MySQL Database is a very popular solution for the cache storage. The new records are created in the "core_cache" table with every new visited page. The solution is scalable. In case a store is replicated on several servers in order to balance site load, the database can be used as a common cache storage for numerous Magento nodes.
Moreover, it does not require any special skills to enable it.

File System is another solution to store cache. The cached data is stored in files on a disk. You can find them on a server in the magento_installation_folder/var/cache/ folder. The solution is available out of the box. So, there is no need to deal with configuration. In order to flush the cache it is required to remove all files from the var/cache/ with server access details.
To store cache in files you can just create a custom text file in the Magento root.

Memcached means "memory cached," which is simply caching resources in the memory. These resources can be data retrieved from API calls, database operations or even HTML pages. The data is stored in key/value pairs in the form of large hash tables. To use Memcache it should be installed and configured on a server. However, it is not a popular method of cache storage since it does not support tags and autoflush caching will not work as well. For example, when we save a product cache will not be cached automatically.

You can enable or disable separate design for mobile devices and PC.

The links are being crawled in the order they appear in the text file. It is possible to move a link up in the list for it to be crawled sooner. Please keep in mind that Full Page Cache Warmer doesn't influence the caches, it just takes the pages from default Magento URL rewrite tables and "warms" them so that they are cached even before the first customer opens a page.

Decrease the time of cache living or move the cache storage to the Redis or text files.

Consult our user guide to learn how to switch to the text file.

The files will store caches of the page, the caches of the individual blocks will remain in core_cache.

To learn how to move the cache to Redis, please consult the following guide. 

If the Redis is used the full page cache will be stored in it.

One more solution is to decrease the number of page combinations for Crawler:

It will help to reduce the number of combinations for each link when Crawler keeps your cache 'warm'.