Master LiteSpeed Object Cache: LSCache + Redis for Heavy Multisite WordPress Networks

Running a large WordPress multisite network can be a real performance challenge. With dozens—or even hundreds—of sites pulling content from the same database, page‑load times can quickly degrade, especially under heavy traffic. Fortunately, the combination of LiteSpeed’s built‑in object cache (LSCache) and Redis provides a powerful, low‑latency caching layer that offloads database queries and dramatically speeds up dynamic content delivery.

Why LSCache + Redis Is the Ideal Pair for Multisite

LiteSpeed Web Server already excels at serving static assets with its event‑driven architecture. When you enable LSCache, LiteSpeed can also cache WordPress objects—queries, transients, and more—directly in memory, eliminating the need for repeated database hits. Redis, an in‑memory key‑value store, complements LSCache by offering a fast, persistent storage backend that can handle millions of keys with sub‑millisecond latency.

• Scalability: Redis scales horizontally with clustering, making it perfect for networks that grow over time.
• Isolation: Each site in a multisite can have its own cache prefix, preventing cross‑site data leakage.
• Persistence: Unlike pure memory caches, Redis can snapshot data to disk, protecting against data loss on server restarts.
• Compatibility: LSCache’s native Redis driver integrates seamlessly with the LiteSpeed Cache plugin, requiring minimal configuration.

Prerequisites Before You Begin

Before diving into the configuration steps, make sure your environment meets the following requirements:

1. LiteSpeed Enterprise or OpenLiteSpeed: The LSCache plugin works with both, but Enterprise offers additional performance‑tuning options.
2. Redis Server Installed: Redis 5.0+ is recommended. Install it via your package manager (e.g., apt-get install redis-server or yum install redis).
3. PHP Redis Extension: The php-redis extension must be enabled so WordPress can communicate with Redis.
4. LiteSpeed Cache Plugin: Install and activate the latest version from the WordPress plugin repository.
5. Root or Sudo Access: Required for editing server configuration files and restarting services.

Step‑By‑Step Configuration

1. Secure and Optimize Redis

Start by configuring Redis for a production environment. Edit /etc/redis/redis.conf (the path may vary) and apply the following changes:

• bind 127.0.0.1 – Restricts access to localhost only.
• protected-mode yes – Prevents unauthenticated external connections.
• maxmemory 2gb – Adjust based on your server’s RAM; this caps Redis’s memory usage.
• maxmemory-policy allkeys-lru – Evicts the least‑recently‑used keys when the limit is reached.
• appendonly yes – Enables AOF persistence for durability.

After saving the file, restart Redis:

sudo systemctl restart redis
sudo systemctl enable redis

2. Enable LSCache Object Cache in LiteSpeed

Log in to your LiteSpeed Web Admin console (usually https://your‑server:7080) and navigate to Cache → Cache Settings → Object Cache. Perform the following actions:

1. Set Cache Type to Redis.
2. Enter the Redis host (127.0.0.1) and port (6379 by default).
3. If you enabled a password in redis.conf, fill in the Auth Password field.
4. Define a Cache Prefix. For multisite, use a dynamic placeholder: lscache_$blog_id_. This ensures each site gets its own namespace.
5. Set TTL (Time To Live) to a sensible default, such as 300 seconds (5 minutes). You can fine‑tune per‑site later.
6. Click Save and then Restart LSWS to apply changes.

3. Configure the LiteSpeed Cache Plugin for Multisite

Within the WordPress Network Admin, go to Litespeed Cache → Settings → Cache. Enable the following options:

• Object Cache – Turn it On.
• Cache Object Store – Choose Redis.
• Cache Object Prefix – Use the same placeholder as in LSWS: lscache_$blog_id_.

Next, head to Litespeed Cache → Settings → Advanced → Object Cache and set:

• Redis Host: 127.0.0.1
• Redis Port: 6379
• Redis Password: (if set)
• Persistent Connection: Yes (reduces connection overhead).

Save all settings. The plugin now talks directly to Redis, while LiteSpeed serves cached objects at the server level.

4. Fine‑Tune Per‑Site Cache Policies

Even within a single network, different sites may have varying traffic patterns. You can override global settings on a per‑site basis:

1. Switch to the individual site’s admin dashboard.
2. Navigate to Litespeed Cache → Settings → Cache.
3. Adjust Object Cache TTL and enable/disable specific object types (e.g., WP_Query, transients).
4. Use the Cache Excludes tab to prevent caching of admin‑only queries or personalized content.

For high‑traffic blogs, a longer TTL (e.g., 900 seconds) can reduce load, while e‑commerce subsites may need a shorter TTL to keep product availability fresh.

Testing and Monitoring

Verify Cache Hits

After configuration, you should see a high proportion of cache hits. Use the following methods to confirm:

• LiteSpeed Dashboard: Under Cache → Statistics, the “Object Cache Hit Rate” should be above 80 %.
• Redis CLI: Run redis-cli info stats and look for keyspace_hits vs. keyspace_misses.
• Browser DevTools: Check response headers for X-LiteSpeed-Cache: hit and X-LiteSpeed-Cache-Object: hit.

Monitor Performance Over Time

Long‑term health of the cache layer can be tracked with tools like Grafana + Prometheus or the built‑in LiteSpeed Real‑Time Stats. Key metrics to watch:

1. Object cache hit ratio.
2. Redis memory usage vs. maxmemory limit.
3. Eviction count (high evictions may indicate a need to increase maxmemory).
4. CPU load on the web server—LSCache should keep it low even under spikes.

Common Pitfalls and How to Avoid Them

• Cross‑Site Cache Pollution: Forgetting the $blog_id prefix can cause one site’s cached queries to be served to another. Always verify the prefix in both LSWS and the plugin.
• Redis Authentication Mismatch: If you set a password in redis.conf but forget to add it to LSCache settings, the connection will silently fail, resulting in a 0 % hit rate.
• Insufficient Memory: A low maxmemory setting leads to frequent evictions, negating the benefits of caching. Monitor and adjust based on traffic patterns.
• Object Cache Disabled on Critical Plugins: Some plugins (e.g., WooCommerce) rely on dynamic queries. Use the “Cache Excludes” tab to fine‑tune rather than turning off the entire object cache.

Conclusion

Configuring LiteSpeed’s object cache to use Redis transforms a heavy WordPress multisite network from a sluggish, database‑bound beast into a lightning‑fast, scalable platform. By securing Redis, aligning prefixes, and fine‑tuning per‑site policies, you ensure that each site benefits from isolated, high‑performance caching while maintaining data integrity. Continuous monitoring will help you keep the cache healthy as your network grows, delivering a seamless experience for visitors and reducing server costs.

Ready to boost your multisite? Follow the steps above, test rigorously, and watch your page‑load times plummet. Happy caching!