Drupal is a registered trademark of Dries Buytaert
cms 2.1.3 — Update released for Drupal core (2.1.3)! drupal 10.5.11 — Update released for Drupal core (10.5.11)! drupal 11.3.11 — Update released for Drupal core (11.3.11)! drupal 11.2.13 — Update released for Drupal core (11.2.13)! drupal 10.6.10 — Update released for Drupal core (10.6.10)! cms 2.1.2 — Update released for Drupal core (2.1.2)! drupal 11.1.10 — Update released for Drupal core (11.1.10)! drupal 10.5.10 — Update released for Drupal core (10.5.10)! drupal 10.4.10 — Update released for Drupal core (10.4.10)! drupal 11.2.12 — Update released for Drupal core (11.2.12)! drupal 11.3.10 — Update released for Drupal core (11.3.10)! drupal 10.6.9 — Update released for Drupal core (10.6.9)! drupal 10.6.8 — Update released for Drupal core (10.6.8)! drupal 11.3.9 — Update released for Drupal core (11.3.9)! drupal 11.3.8 — Update released for Drupal core (11.3.8)! drupal 11.3.7 — Update released for Drupal core (11.3.7)! drupal 11.2.11 — Update released for Drupal core (11.2.11)! drupal 10.6.7 — Update released for Drupal core (10.6.7)! drupal 10.5.9 — Update released for Drupal core (10.5.9)! cms 2.1.1 — Update released for Drupal core (2.1.1)!
← All modules

purge_adaptive_capacity

No security coverage
View on drupal.org

Purge processes its queue in fixed-size chunks per cron run (often 100 items), set by the active purger. When cache invalidations are produced faster than they are processed — or when cron is delayed — the queue grows and never catches up.

Purge Adaptive Capacity scales the number of items processed per cron run based on the current queue size: more items when the backlog grows toward a configurable high-watermark, fewer when it shrinks (never below a configurable minimum). This keeps the queue under control without permanently over-processing.

Features

  • Scales the per-cron processing limit linearly with the queue size.
  • Configurable minimum (hard floor of 100), maximum, and queue high-watermark.
  • Purger-agnostic: decorates Purge's capacity tracker, so it works with any purger.
  • Respects Purge's execution-time safeguards — the limit acts as an upper bound.
  • Can be disabled to fall back to the standard purger capacity.

Post-Installation

After enabling the module, go to Administration » Configuration » Development » Purge adaptive capacity (/admin/config/development/performance/purge-adaptive-capacity) and set the minimum items, maximum items, and queue high-watermark. The scaling formula is: limit = min_items + (max_items - min_items) * min(1, queue_size / queue_high_watermark).

Additional Requirements

Requires the Purge module.

Similar projects

Unlike static configuration of a purger's capacity, this module adjusts the limit dynamically at runtime based on the live queue size.

Activity

Total releases
2
First release
Jun 2026
Latest release
16 hours ago
Release cadence
0 days
Stability
50% stable

Releases

Version Type Release date
1.0.x-dev Dev Jun 16, 2026
1.0.0 Stable Jun 16, 2026