What Is Brim's Full Page Cache?
Brim's Full Page Cache decreases the time it takes to generate product, category, and CMS pages. Additional pages may also be cached. This means pages will be delivered to your customers faster and with much less of a load on your servers.
How Does It Work?
When visiting a website, a cache page is created for individual customers. The cache is then held until the duration of the set time expires. Any of the site's pages not visited by the customer remains a Magento-fetched page. When new customers visit the site within the set expiration time, the frontpage, along with other pages visited by previous customers are now cached. This process reduces the load on your servers, while increasing your page speed, and ultimately constructs a faster customer experience within your site.
What are your recommended settings for the cache backend?
Most stores will benefit from splitting the full page cache backend from the standard Magento cache backend. This can be done via System > Configuration > Full Page Cache > Storage Settings.
- Use System Cache = "No"
- Type = "File"
- Path = "cache-fpc"
Based on the number of products, categories, and CMS pages you have in your store File may not be a suitable backend choice as it does have issues flushing the cache when it's very large. Or if you have multiple web servers you will want to choose a backend designed to handle that configuration. Here are our basic guidelines:
- If you have one web server
- If you have limited number of products use
- APC, File or Database as the slow type
- If you have many products use
- If you have multiple web servers use
- Memcached, Database as the slow type
- Redis (Magento CE 1.8+ required & Brim's FPC 3.1+)