Full Page Cache
Find Hole Punches and Invalidate Selectively
The Full Page Cache is one of the biggest performance levers in Magento 2, but also a frequent source of errors. Anyone who wires dynamic content in the wrong way or invalidates the cache too bluntly loses hit rate, speed and often functional correctness as well.
Table of Contents
- 1. What Full Page Cache actually does in Magento 2
- 2. Thinking clearly about dynamic content and hole punches
- 3. Private Content instead of destroying the cache
- 4. Selective invalidation instead of a global flush
- 5. Analyzing FPC in everyday project work
- 6. Common mistakes
- 7. Full caching vs. dynamic convenience
- 8. Magento 2 support
- 9. Summary
- 10. FAQ
1. What Full Page Cache actually does in Magento 2
The Full Page Cache Magento 2 stores complete page output so identical requests do not have to run through the entire rendering, data loading and block system