Wednesday 05 June 2013 2:46:43 pm
This series of articles provides a rather advanced clarification on the operations of the cache in eZ Publish. This article if the last of the series.
Don't forget to read the previous parts of the series:
This series of articles provides a rather advanced clarification on the operations of the cache in eZ Publish, with a particular focus on:
This series of articles will attempt to avoid explaining once again what is already comprehensible and has been fully described in other tutorials or official documentations, it aims:
To all those who consider that eZ Publish cache management is complex and / or problematic, it is also necessary to consider the following :
Note: The mechanisms and examples described are based on version 4.5+ Enterprise of eZ Publish or eZ Publish 2012.x Community (until 2012.8 or later in the Legacy Stack part of the builds).
eZ Publish is an infinitely flexible and powerful CMS that powers a wide variety of websites with low or high traffic. This power comes with a price: resource consumption in general, and SQL resource consumption in particular, as well as disk I/O ! All these mechanisms have to be controlled to size its architecture, or understand the impact of a parameter, of a cache-block directive or even a massive removal of cache (template, cache-block or view cache).
The previous articles detailed templates compilation, view caches and how to optimize template-block caches to ensure the sustainability of an eZ Publish project over time. This article, that closes the series of four articles on eZ Publish caches, details the role of the expiry.php file and the way the ezcache.php script works.
This series of articles is aimed mainly to:
WARNING: Reading this tutorial may be particularly painful and requires concentration and a long-lasting patience. It is advisable to read it in multiple sessions, equipped with a beer or a good bottle of wine for the wealthiest among us.