Operate
Configuration & topologies
Match cache behavior to your Redis topology and operational needs.
Standalone, Cluster and Sentinel
Free supports a single Redis server. The Pro code contains standalone, replication, Cluster and Sentinel paths. Existing tests exercise bounded scenarios; they do not establish every network partition or workload. Relay requires its own runtime verification.
Request-local negative caching
negative_cache defaults to false. When enabled in WP_REDIS_CONFIG, genuine misses are remembered for the current cache instance until the request ends or runtime cache is flushed. Forced reads bypass remembered misses.
// Add to the existing WP_REDIS_CONFIG array:
'negative_cache' => true,Separate installations
Use distinct prefixes for unrelated installations sharing Redis. Multisite scopes and global groups are separate cache concepts; review namespace behavior before changing a prefix or topology. A prefix change starts a cold cache.