Superpowers Sage Acorn Redis

Redis with Acorn in WordPress

When to use

• Object cache for WordPress (wp_cache_*) backed by Redis instead of ephemeral in-process cache
• Laravel cache / session / queue driver inside theme code
• Cross-request rate limiting, lock coordination, or atomic counters
• High-traffic sites where wp_options autoload pressure needs relief
• Queue backend for acorn-queues when jobs need durable storage beyond sync driver

When NOT to use

• Small dev-only sites with no performance pressure — array/file cache is fine
• Shared hosting without Redis — use file or database cache driver instead
• As a database — Redis is cache; persistent data belongs in MySQL
• When wp_cache_* calls are rare and localized — flushing coordination overhead may exceed benefit

Prerequisites