Redis is now available across our LiteSpeed (LSWS) network. It is optional: you turn it on per hosting account when you want object cache, and leave it off if you do not.
LiteSpeed already caches finished HTML pages for guests. Redis sits beside that. It keeps WordPress (and similar PHP apps) from asking MySQL the same questions over and over — options, transients, WooCommerce fragments, logged-in dashboards. Page cache and object cache are different layers. You want both on a busy site.
What Redis does
Redis is an in-memory store. Data lives in RAM on the server, so reads are measured in microseconds instead of a round trip to the database. WordPress uses it as an object cache: the result of a query is remembered until it changes, then served from Redis.
That helps most when:
- people are logged in (page cache cannot be used for them)
- the site hits the database hard — WooCommerce, LMS, membership, busy wp-admin
- the same options and lookups run on every request
It will not magically speed up a slow plugin, and it is not a replacement for LiteSpeed Cache’s page cache. Guests still get HTML from LSCache. Redis helps PHP and MySQL for the work that still has to run.
How it works on our platform
We run Redis Per User, not a single shared Redis on port 6379. Each account that enables it gets its own Redis process and a Unix socket in the home directory:
/home/YOURUSER/.redis/redis.sock
Nothing listens on 6379 for your neighbours. Your site talks to your socket only. That is the safe model on shared and agency servers — a shared TCP Redis would let one account read another account’s cache.
It stays off until you enable it for that account. Other sites on the same server are unaffected.
How Redis works with LiteSpeed (LSWS)
LiteSpeed Web Server plus the LiteSpeed Cache plugin already give you LSCache: full-page cache, image optimisation, and the rest of the WordPress cache toolbar you already use.
Object cache is a second switch inside that same plugin. PHP still needs the Redis extension loaded, then LiteSpeed Cache talks to your per-user socket:
- LSCache (page cache) — stores finished HTML for anonymous visitors
- Redis (object cache) — stores WordPress objects in RAM for PHP
- LiteSpeed Cache plugin — Cache → Object is the control panel that joins the two
The existing object-cache.php drop-in from LiteSpeed Cache stays in place. Once Redis is running and the plugin is pointed at your socket, that drop-in gets a real backend instead of “not connected”.
Enable it per account
Redis is not switched on for every site. Enable it only where it is useful.
- In Webuzo, open Redis Wizard and start Redis for that account. Copy the socket path.
- In Configuration → PHP Extension, pick the PHP version the site uses. Enable igbinary, then msgpack if it is listed, then redis. Save.
- In WordPress, open LiteSpeed Cache → Cache → Object. Turn object cache on, method Redis, host
/home/YOURUSER/.redis/redis.sock, port0. Save and confirm it says connected.
Full screenshots and the exact plugin fields are in the client area knowledge base: How to enable Redis object cache with LiteSpeed.
If you would rather we switch it on for you, open a support ticket and include the hosting username.
