Caching Dynamic Snippets in Evolution CMS Without Losing Dynamic Output

One of the hardest parts of optimizing older Evolution sites was dealing with snippets that were expensive but still needed fresh output. The old community discussed this problem deeply, and this article preserves one of the more thoughtful takes on how to approach it.

Main idea

Instead of disabling cache for the whole page, isolate the dynamic region and control when that piece gets refreshed. The goal is to keep cache working for the static majority of the page while preserving the behavior of the expensive block.

Why this matters

• it keeps the site fast without turning every page into uncached output
• it reduces unnecessary database load on high-traffic pages
• it reflects a serious engineering concern in the old Evo community, not just a template trick

Historically, this is one of the more valuable archive pieces because it documents how developers thought about performance as a system problem, not only a snippet problem.