If you’re running the Redis Object Cache plugin and wondering whether it’ll cause any conflict with BerqWP, the short answer is no. This article explains why, and what Redis Object Cache actually does versus what BerqWP handles.
TL;DR: BerqWP works flawlessly alongside the Redis Object Cache plugin, with zero configuration needed on either side. They cache different things, BerqWP caches your pages, Redis Object Cache caches your database queries, so there’s no overlap or conflict to manage.
Why BerqWP and Redis Object Cache Don’t Conflict
BerqWP and Redis Object Cache solve different problems. BerqWP’s page caching stores a ready-to-serve version of your full pages, so repeat visitors get a fast result without WordPress rebuilding the page from scratch. Redis Object Cache works underneath that, at the database query level, storing the results of repeated database lookups so WordPress doesn’t have to run the same query over and over.
Since they’re operating on different layers, there’s no setting in either plugin you need to adjust, no exclusion list to maintain, and no whitelisting step required. You can activate both and they simply work together.
What Redis Object Cache Actually Requires (Separate From BerqWP)
It’s worth being clear about what “zero configuration” applies to here. The compatibility between BerqWP and the Redis Object Cache plugin itself needs no setup. That’s different from getting Redis running on your server in the first place, which is a separate, server-level task that has nothing to do with BerqWP. Redis itself typically needs to be installed on your hosting environment, often with specific memory limits and an eviction policy configured, before the WordPress plugin has anything to connect to. If your host offers Redis (many managed WordPress hosts do, often with one-click setup), that part is usually already handled for you. If you’re setting up Redis yourself on a generic server, that configuration is real work, just not work that involves BerqWP at all.
A Redis Object Cache Compatibility Note Worth Knowing
If you’re also considering LiteSpeed Cache, be aware that LiteSpeed Cache’s own built-in object cache feature should not be enabled at the same time as the Redis Object Cache plugin, running both at once is a known source of conflicts. This isn’t a BerqWP-specific issue, it applies regardless of which page caching plugin you use alongside Redis.
Do You Need to Configure Anything in BerqWP?
If you already have Redis running on your server and the Redis Object Cache plugin active, you don’t need to change anything in BerqWP to make them work together. Just keep both active as normal, and BerqWP will continue handling page caching and optimization exactly as it already does.
