What to Check When the Evolution Cache Directory Fills with Thousands of Files

The old case behind this post described an Evolution build where the cache directory under /assets/cache/ contained thousands of files. That can look alarming, but the right response depends on why the files are being created.

What to Review

• how often content is being regenerated
• whether query-driven page variants are multiplying cache output
• whether expired cache files are being cleaned up properly
• whether the project is caching pages that should not be cached at all

When It Is Normal

A busy content site can legitimately produce a lot of cache files. That alone does not prove something is wrong.

When It Is a Warning Sign

If the cache count grows far beyond expected page volume, or if it expands rapidly after search, filtering, or ad-landing logic is added, then the caching rules probably need a tighter scope.

The best response is not to delete files blindly, but to understand which request patterns are generating them and whether those variants are worth caching in the first place.