Blog Sections Open
Speeding Up AjaxSearch on Large YAMS Sites with TV-Based Content
Search becomes painfully slow when every request has to scan many TVs across a multilingual site. The answer is to reduce what gets searched and how often it is joined.
AjaxSearch can become extremely slow on multilingual Evolution CMS sites that store most content inside TVs, especially when YAMS is involved. In that setup, each search request can turn into a heavy scan across many template-variable records instead of a small query against core fields.
What usually helps most
- search fewer TV fields and index only the ones that matter
- precompute searchable text instead of assembling it on every request
- limit results early by section, language, or content type
- cache frequent search fragments where the UX allows it
Structural takeaway
If most user-facing text lives in TVs, search is no longer a small addon feature. It becomes a data-modeling concern. At some scale the best optimization is not another query tweak, but changing how searchable content is stored.
How to Verify That Caching Is Actually Working in Evolution CMS
A practical checklist for confirming whether cached snippets and cached page output are really being served in Evolution CMS.
Fixing Blank Pages After Scheduled Unpublish Events with Cache Enabled
Why scheduled resource state changes can leave stale empty pages in cache and how to handle the cache layer correctly.