Blitz creates thousands of cache-regeneration jobs for centrally referenced entries, blocking editor updates #866
Description
Feature Request
Context
- Site size: ~15,000 pages.
- Content model: Several "central" entries are referenced across many pages; some central entries appear on nearly every page.
- Caching: We use the Blitz plugin to generate static HTML per page.
Observed behavior
- When a central entry is updated, Blitz invalidates all pages that reference it and enqueues cache-regeneration jobs for each affected page.
- This results in tens of thousands of queue jobs (e.g. ~30k).
- Blitz enqueues these jobs on our custom blitz queue, filling it and delaying processing of other jobs.
- Editor-initiated updates (content edits that should be processed interactively) are pushed behind the Blitz jobs and therefore are processed much later (sometimes hours).
Why job priority is (probably) not usable
- Job priority only helps if you can assign different priorities depending on job origin.
- In our setup there is no mechanism to tell the queue “this job was generated by an editor change” vs. “this job was created by blitz’s bulk regeneration”, so we cannot reliably set different priorities at enqueue time.
Impact
- Long delays between saving content and seeing updated pages.
Feature request proposal
- Introduce a dedicated Blitz queue used solely for entries modified directly via the editor interface (e.g. content saved in the Control Panel). This queue would contain only jobs triggered by editor actions.
- Or provide a mechanism to set priority for queue jobs initiated by editor events (e.g. the onSave event), so these jobs can be prioritized over bulk Blitz regeneration jobs.
Plugin Version
No response