Abstract

For high-traffic WordPress sites, the MySQL database is the primary bottleneck. Redis Object Caching alleviates this pressure by storing the results of complex database queries in RAM. This chapter details the technical configuration of persistent Redis caching for 2025, covering the WP_REDIS_CONFIG constants, eviction policies, and monitoring strategies necessary for stability.

The Role of Object Caching

WordPress includes an internal Object Cache API, but by default, it is non-persistent. Data stored in the cache (like the result of get_options) persists only for the milliseconds it takes to generate a single page. Once the page is sent, the cache is discarded.

Redis Persistence:

By installing a persistent object cache (like Redis), this data survives across requests.

1. Request A: WordPress queries the database for the site options. The result is stored in Redis.
2. Request B: WordPress checks Redis first. It finds the data and serves it instantly (microseconds), bypassing the slower SQL database (milliseconds).
   This mechanism is critical for dynamic content (like logged-in user dashboards or WooCommerce carts) where full-page caching is not possible.

Critical Configuration: WP_REDIS_CONFIG

To ensure a robust connection, configuration should be defined in wp-config.php rather than relying on plugin UI settings. This ensures settings persist through deployments and plugin updates.

define('WP_REDIS_CONFIG',);

Key Optimization:

The split_alloptions parameter is vital. The alloptions array in WordPress can be massive. Redis performance degrades when fetching large keys. This setting splits that array into individual keys, allowing for faster, more granular retrieval.35 The prefix is also mandatory on shared Redis servers to prevent cache collisions between staging and production environments.

Eviction Policies

Redis stores data in RAM, which is finite. When memory is full, Redis must decide what to delete to make room for new data.

• Bad Policy: noeviction (Default). Redis returns an error when full, causing the site to crash.
• Good Policy: allkeys-lru (Least Recently Used). Redis deletes the keys that haven’t been used recently to free up space. This ensures the “hot” data remains cached while the site stays stable.

Monitoring with WP-CLI

The wp redis command set is essential for debugging.

• wp redis enable: Connects the drop-in.

wp redis status: Displays connection health and hit ratio.
A healthy Redis setup should see a hit ratio above 90%. If the ratio is low, it indicates that the cache is being flushed too frequently (perhaps by a plugin triggering wp_cache_flush aggressively) or that the eviction policy is too aggressive due to insufficient RAM allocation.