LumenCache
LumenCache implements a RAM-first full-page cache with a WordPress advanced-cache.php drop-in. On a cache HIT, the drop-in serves complete HTML before the normal WordPress bootstrap and database queries. This early-response path reduces application-layer work and keeps repeat page requests fast across Nginx, Apache, and LiteSpeed.
The cache is designed to fail open when its storage layer is unavailable, so a cache connection problem does not take the WordPress site offline.
Research Foundation
Academic Reference: “Dynamic Resource Mapping in Zero-Reload Server Architectures: Eliminating Application-Layer Latency and Extension Dependency in High-Concurrency CMS personalised requests continue through the full WordPress stack.
This architecture is intended to reduce repeated bootstrap work, database queries, and extension overhead while preserving WordPress compatibility. It also provides a practical bridge between academic performance research and everyday publishing workloads, including content-heavy sites, WooCommerce catalogues, and membership-driven pages.
Research author: Dean Nasrul Eam — Light & Composition University.
Eight-Subsystem Architecture
- RAM-First Full-Page Cache Engine — PHP stores complete HTML at shutdown and resolves repeat requests from the in-memory cache layer.
- Nginx / Apache Proxy Bridge — Static or dynamic server config bypasses PHP entirely for cache hits.
- Selective Bypass Cookie Router —
sys_active_statecookie routes logged-in users and cart-active visitors to live PHP. - Application Driver Profile Engine — Auto-detects WooCommerce, LearnDash, LifterLMS, MemberPress, BuddyBoss and registers tailored bypass rules and invalidation hooks.
- Surgical Cache Invalidation — Post save / nav menu / widget / theme switch events trigger precise per-URL or full purges.
- REST API State Endpoint —
/wp-json/lumencache/v1/user-stateserves personalised fragments for skeleton-hydration clients. - Skeleton Hydration DOM Worker —
skeleton-hydration.jsreplaces cached placeholders with live content on load. - WP-CLI Management Interface —
flush,flush-url,statuscommands.
Configuration (optional)
All settings are configurable from LumenCache → Settings in the WordPress admin. Optionally override any setting via wp-config.php — constants always win:
define( 'LUMENCACHE_REDIS_HOST', '127.0.0.1' );
define( 'LUMENCACHE_REDIS_PORT', 6379 );
define( 'LUMENCACHE_REDIS_SOCKET', '' );
define( 'LUMENCACHE_REDIS_PASSWORD', '' );
define( 'LUMENCACHE_REDIS_DATABASE', 0 );
define( 'LUMENCACHE_REDIS_TIMEOUT', 1.0 );
define( 'LUMENCACHE_REDIS_PREFIX', 'cache:' );
define( 'LUMENCACHE_CACHE_TTL', 86400 );
define( 'LUMENCACHE_CACHE_SALT', '' );
define( 'LUMENCACHE_CACHE_QUERY_STRINGS', false );
define( 'LUMENCACHE_PROXY_PASSWORD', '' );
WP-CLI
wp lumencache flush
wp lumencache flush-url https://example.com/page/
wp lumencache status<h3>Privacy</h3>
LumenCache stores rendered page HTML and cache metadata in the in-memory cache service configured by the site administrator. It does not send cache contents, visitor data, or analytics data to a third-party LumenCache service. The optional user-state endpoint returns only the requested dynamic values to the requesting browser; sites should review those values and their own privacy policy before enabling personalized hydration.