Blog Sections Open
Measuring CacheAccelerator Gains on News Pages with Heavy Ditto and Jot Usage
A historical performance note about where page-level caching helps and where Jot-heavy pages still need structural optimization.
One of the more useful old performance discussions around Evolution CMS was not about a single broken snippet, but about measuring what actually changed after enabling a cache layer on a busy news site.
The scenario
The project used multiple Ditto calls, Wayfinder menus, tags, search, and article pages with Jot comments. On the homepage, CacheAccelerator delivered a visible drop in queries and render time. On news detail pages with comments, the gains were much smaller.
Why that was useful
The real lesson was not “cache does not work.” It was that page-level cache helps most when the page is dominated by repeatable list output. Once a page includes comment flows, multiple uncached fragments, and dynamic blocks, the request budget is governed more by composition than by the presence of one cache plugin.
What this adds to the archive
This topic gives the historical timeline something important: real numbers and a practical way of thinking about performance. Evolution CMS tuning was often about deciding which parts of the page could be made static, which parts had to stay dynamic, and which snippet calls had become too expensive to keep stacking.
Related posts
Reducing Homepage Overhead When Multiple Ditto Calls Compete on One Page
Understanding siteCache.idx.php and Evolution CMS Cache Internals
Caching Dynamic Snippets in Evolution CMS Without Losing Dynamic Output
Sanitizing Stored TV IDs Before getDocuments Queries in Evolution CMS
A defensive API fix for avoiding SQL errors when malformed TV values are passed into getDocuments.
Keeping Jot Placeholders Working on Cached Pages
A historical workaround for keeping Jot output alive even when the page itself remains cached.