Making site slower

Hi @mackiller,

Thanks for trying out WP LCache.

To provide a bit of background, WP LCache takes a two tier caching approach:

* Cache persistence is managed by the L2 cache, your database. Every cache entry is written to your database too.
* Cache performance is managed by the L1 cache, APCu. Cache entries are read from the database into APCu (which is in PHP memory), and then served directly from APCu.

When you first enable WP LCache, you’ll have a good amount of database activity as it writes all cache entries to the database. Eventually, as long as your codebase is optimized, database activity will die down and most activity will be in APCu.

However, if your codebase isn’t optimized, you’ll see continued database load. Some common issues include:

* Frequent calls to wp_cache_flush(), which empties the entire cache and requires the L2 to be completely repopulated.
* Redundant or duplicative calls to wp_cache_set(), where code paths hardly ever use the cache values they set.

In both of these cases, any persistent object cache drop-in probably isn’t going to be useful until you solve your code problems.

Hope this helps clarify!

Thank you. For this cause, I went back and forth to the same pages, hoping that it would get faster after the cache was filled in and stable. I am not using anything major, just a vanilla page with no plugins, but divi theme loaded.

So, this was on a low traffic dev site. Is it possible that we would only see the advantages on a high traffic site, but could actually experience a slow down on a low traffic site?

Is it possible that we would only see the advantages on a high traffic site, but could actually experience a slow down on a low traffic site

Yes, as with any object cache drop-in. There’s a certain amount of overhead in using a persistent object cache (network I/O, etc.), so you need to make sure the benefits outweigh the costs.