WPVELOCITY PLAYBOOK 08 • REDIS IN-MEMORY OBJECT CACHE TUNING
WPVelocity Runbook: Redis 7 Unix Sockets, LRU Eviction & Autoload Hygiene
We show how moving Redis from TCP loopback to Unix domain sockets with `igbinary` serialization, `allkeys-lru` eviction, and pruned `wp_options` autoload rows eliminates dynamic CPU overhead. (WPVelocity Modeled Targets: 118 ms (Unix Socket) • 1.2s Modeled LCP • 64 ms Modeled INP).
WPVelocity Engineering Note: Default Redis setups over `127.0.0.1:6379` using uncompressed text PHP serialization spend substantial CPU time deserializing multi-megabyte `alloptions` blobs across dozens of `get()` calls per page. Switching to Unix sockets plus compiled `igbinary` shrinks memory footprint by roughly 50% and removes TCP stack overhead.
Load Preset in WPVelocity PHP Worker Calculator →
WPVelocity Serialization Audit: TCP Loopback & Bloated alloptions Hashes
Under our WPVelocity queueing equations, unoptimized defaults push dynamic origin responses toward 640 ms (TCP SQL) under concurrent load.
WPVelocity /etc/redis/redis.conf Ephemeral Object Cache Config
# /etc/redis/redis.conf — WPVelocity Unix Socket + Safe LRU Eviction
unixsocket /var/run/redis/redis.sock
unixsocketperm 770
maxmemory 2gb
maxmemory-policy allkeys-lru
save ""
appendonly no
lazyfree-lazy-eviction yes
WPVelocity Persistent Cutover Checklist (REDIS-SOCKET)
-
Enforce `maxmemory-policy allkeys-lru` (never `noeviction`, which throws fatal OOM exceptions on checkout once maxmemory fills).
wp plugin list --status=active --format=table --allow-root
-
Disable RDB/AOF disk snapshots (`save ""`, `appendonly no`) when Redis serves purely as an ephemeral WordPress Object Cache.
wp cache flush --allow-root && redis-cli -s /var/run/redis/redis.sock info memory
-
Audit `wp_options` rows where `autoload="yes"` — prune orphaned plugin rows exceeding 100 KB so `alloptions` stays lean.
curl -I https://store.yourdomain.tld/ | grep -iE "x-litespeed-cache|cf-cache-status"
-
Enable `php8.3-redis` compiled with `igbinary` support so cached object arrays serialize compactly in RAM.
systemctl status wp-action-scheduler.timer --no-pager
WPVelocity Concurrency & Tier Sizing Matrix (2026-11-12)
WPVelocity Rate Notice: Public rates retrieved 2026-11-12 from each vendor’s official pricing page; promotional introductory discounts and multi-year renewal prices may change at any time — always verify exact billing terms on the vendor’s official checkout page before purchasing.
3.5GHZ+ HIGH FREQUENCY
From $12/mo
WPVelocity: Vultr High Frequency 3.5GHz+ NVMe Cloud (SG / Tokyo)
3.5GHz+ Turbo Single-Thread PHP Execution • Direct Singapore & Tokyo Peering • Hourly Scaling (OpenLiteSpeed / RunCloud / SpinupWP / GridPane Ready • Redis Pro / Relay In-Memory PHP Extension Ready).
Inspect Vultr Specs via WPVelocity ↗
CYBERPANEL / CLOUDPANEL KVM
From $5.99/mo
WPVelocity: Hostinger KVM NVMe VPS (CyberPanel / CloudPanel)
Up to 67% OFF + Extra 20% Partner Discount • Dedicated AMD EPYC KVM + 1-Click OpenLiteSpeed (OpenLiteSpeed (CyberPanel) or Nginx FastCGI (CloudPanel) • Dedicated Local Redis 7 Unix Socket (Zero Hop Latency)).
Inspect Hostinger Specs via WPVelocity ↗
WPVelocity Engineering FAQ: REDIS-SOCKET
- Why does WPVelocity check `alloptions` size whenever enabling Redis slows a site down?
- A bloated 4 MB–8 MB `alloptions` payload or a remote TCP Redis host with 3 ms network RTT across 150 calls adds 450 ms+ of serialization and network wait time to every PHP request.
- Is disabling Redis disk persistence (`save ""`) safe in WPVelocity WooCommerce runbooks?
- Yes — MariaDB InnoDB remains the durable database of record for WooCommerce orders; turning off Redis background `bgsave` forks prevents copy-on-write memory spikes during peak sales.