I’m trying to optimize my website for performance and have a question about the database cache.
On my development site, when I run the W3TC setup guide, it indicates memcached as the best choice for database cacheing.
Normally I get the same result on my production site. But today I was doing some testing and noticed the setup guide is telling me to disable the db cache because both memcached and disk options are much slower. See screenshot below (production site on top, development site below).
What do you make of this? Any idea why suddenly the database cache is so slow on the production site but not the dev site? Only difference in setup is that the production site has a remote db server while the development site has a local database right on the web server. Production is also using a CDN.
You think I should just disable db cache on my production site? Seems counter intuitive…
We are considering subscribing to the paid version, but we need to identify the root cause of this issue before making a decision.
]]>When testing Database Cache and Object Cache, if “Disk” is faster than “none”, should I select it?
Thanks very much
]]>The following memcached servers are not responding or not running:
Object Cache: 127.0.0.1:11211.
Database Cache: 127.0.0.1:11211.
This message will automatically disappear once the issue is resolved.
I tried changing Database Cache to Disk – my plan was to save as Disk and then put it back to Memcache – except now I can no longer choose Memcache as the Database Cache Method!!!
Please help!
]]>The following memcached servers are not responding or not running:
Database Cache: 127.0.0.1:11211
This message will automatically disappear once the issue is resolved.
Don’t know how to solve it, and i’ve not access to the server terminal.
Any suggestion? Thanks in advance
`The following memcached servers are not responding or not running:
Database Cache: 127.0.0.1:11211.
This message will automatically disappear once the issue is resolved.`
– Memcached is running on my server
– I use PhP 7.4
– Didn’t have the problem before the update
– All the 3 websites are on 3 different servers but all on the same hosting service (O2siwtch)
I don’t know what to do I tried to change the IP adress and port but so far nothing worked.
]]>We are managing a WordPress installation for one of our customers, however once we enable W3TC and configure the Object and Database Caches (with Redis as backend, 3-server cluster setup) the performance does something funny: Instead of being lower than before, enabling W3TC + object/db cache increases the load by a factor of 4.
How do these caches work under the hood? What do they do? Are there certain plugins or certain ways things can be programmed in which case they should not be used?
CPU/memory/hardware should not be a limitation, it’s a 3-server setup running HAProxy, Varnish (currently not caching) and Apache MPM preforked with Redis as caching backend.
Looking forward to your feedback.
]]>(sorry for my english. I’m using translate)
]]>Notice: Undefined index: options in ./wp-content/plugins/w3-total-cache/Cache_Redis.php on line 181
Notice: Undefined index: remaining in ./wp-content/plugins/w3-total-cache/Cache_Redis.php on line 181
Notice: Undefined index: comments in ./wp-content/plugins/w3-total-cache/Cache_Redis.php on line 181
Notice: Undefined index: singletables in ./wp-content/plugins/w3-total-cache/Cache_Redis.php on line 181
]]>After further investigation, here were the issues/environment:
– Cloud Dedicated Server (Linux, Apache, PHP-FPM)
– Using Memcache
– Database Cache enabled (using Memcache)
– Sites affected were installed in different directories on the same domain & cPanel account
– Even if we migrated the sites to their own domains and cPanel accounts, we still experienced the issue
– Single WP installs, not multisite
– The onset of these issues was intermittent, and didn’t occur on all sites at any specific interval, but once it started the only way to fix was to disable W3 Total Cache.
– .htaccess was getting modified with incorrect site redirect info
– Logging into one site would redirect you to a different site, logged in, even if your credentials weren’t for that site.
I assume it has something to do with memcache, and somehow the plugin is looking to the wrong database for information. It just seems like this shouldn’t happen under any circumstances, but it did.
]]>