/tmp/redis.sock and use it as an object cache, which is mostly useful for WordPress.
What it does
Redis is a fast in-memory key-value store. PHP applications can use it as an object cache to skip repeat database queries (option lookups, session reads, expensive query results). On a busy WordPress site, an object cache often cuts TTFB by 30-50% on uncached pages. Without enabling Redis here, an object cache plugin has nowhere to write to. Enable it, point the plugin at/tmp/redis.sock, and the plugin starts caching.
This is not a replacement for page caching. Page caching (LSCache, full-page) serves an entire rendered HTML response. Object caching speeds up the work of generating that response. Use both.
Enable Redis
The page has one main button. If Redis is off, you see Enable Redis Service. If it’s on, you see Disable Redis Service.Click Enable Redis Service
The service starts and the socket appears at
/tmp/redis.sock. Nothing else to do here.Point your app at the socket
For WordPress with LiteSpeed Cache, the plugin auto-detects the socket. For everything else, the connection string is
unix:///tmp/redis.sock with no password.- LSCache for WordPress
- Redis Object Cache (Till Krüss)
- Laravel
WP Admin → LiteSpeed Cache → Cache → Object Cache tab. Enable Object Cache, set Method to Redis, leave Host as
/tmp/redis.sock, leave Port as 0 (UNIX socket). Save.Flush the cache
The Flush Cache button on the page wipes the entire Redis store for your account. Reach for it when:- A stale option is sticking around after you changed it in the database directly.
- You suspect a bad cache entry is causing a bug and want a clean slate.
- You’re testing a cache-related fix.
Settings and Advanced
The two links at the bottom of the page open small popups:| Link | What it does |
|---|---|
| Settings | Adjusts the maxmemory cap for your Redis instance. Defaults are sensible. |
| Advanced | Helper to wire up PHP-FPM session handling to Redis instead of disk-backed sessions. Useful if you have a high-traffic app writing many sessions per second. |
Common issues
LSCache says 'Object Cache Connection Failed'
LSCache says 'Object Cache Connection Failed'
Two usual causes. First, Redis isn’t enabled on this account: open the page and check that the button reads Disable Redis Service (meaning it’s already on). Second, the plugin is pointed at the wrong socket. The socket path is
/tmp/redis.sock, not 127.0.0.1:6379. Set Method to Redis, Host to /tmp/redis.sock, Port to 0.The site is using an old value even after I changed the database
The site is using an old value even after I changed the database
The object cache is serving the stale value. Click Flush Cache here. If you also use LSCache, hit Purge All in the LiteSpeed Cache plugin too.
Redis vs Memcached vs no object cache: which should I pick?
Redis vs Memcached vs no object cache: which should I pick?
Redis on Noxity, every time. Memcached has no advantages over Redis here, and we don’t run Memcached service-side. Without an object cache, WordPress hits MySQL on every uncached page request for
wp_options and similar lookups, which is wasteful on busy sites. The break-even point is roughly 1,000 page views per day; below that, you won’t notice. Above that, Redis pays for itself in TTFB.Disable Redis Service: what happens to my data?
Disable Redis Service: what happens to my data?
Redis is a cache by definition: data in it is disposable. Disabling the service drops the in-memory store. Your site’s persistent data (WordPress posts, options stored in MySQL) is untouched. The next request after re-enabling will rebuild the cache from scratch.
Can I connect over TCP instead of the socket?
Can I connect over TCP instead of the socket?
No. The instance binds only to the local UNIX socket for security. That keeps it scoped to your account; nothing else on the server can read your cache. If your app supports UNIX sockets (most do), use the socket. If it doesn’t, you can run your own Redis from SSH on a high port, but we don’t recommend it; the bundled instance is simpler and is the supported path.