Magento enterprise supports since the 1.7 version the full page cache module: instead of storing only each block content in cache, this is the full page content that’s stored in cache
Everybody agrees this is a really performance enhancement
Like the native cache, storing these datas in a file is not the fastest way and becomes a problem when you need to share it between each front. How can we customize it?
The full_page_cache configuration node in the Magento enterprise.xml file
History of the full page cache configuration in the Magento enterprise versions
Until 184.108.40.206, there was no node to configure the full page cache option in the default Magento enterprise configuration files.
Since 220.127.116.11, you have seen a new node appearing in the app/etc/enterprise.xml file:
This new node allows to customize the cache directory folder where the cache content will be located
Customize your full page cache configuration
Everywhere on the net you can find ways to enhance performance of the Magento cache storage engine by customizing the following configuration node
As with the config > global > cache node, the full page cache node works exactly: all nodes you’ll specify under will configure how full page cache works. For example, The following node defines the usage of memcached as cache storage engine for the full page cache content
Can the full_page_cache node be used within Magento enterprises version prior 1.11?
Yes. Even if this node was initialized in 1.11, all prior versions look for full page cache configuration in this node. So you can also customize your full page cache in all Magento enterprise versions which embeds full page cache module
Don’t forget to customize the full page cache management
As you can see, the two nodes config > global > cache and config > global > full_page_cache are strictly independent: you can provide two different ways to manage cache between Zend cache api and full page cache: we often see that there is cache backend configuration, but do it also for the full page cache