Problematical

Hello @steveatty

Thank you for your review.
Yes, we do have information that some features may actually hurt the website’s performance or styling. It would be very irresponsible for a plugin as big as W3 Total Cache, not to have this kind of information. The reason behind this is that we cannot tell which server, theme, or plugins someone is using.
So if someone is on a shared hosting with limited resources and using for example Object Caching or Database caching with Disk caching method, you are most likely to experience issues with the performance.

Every vehicle has a manual on which gas it runs on and if you put a different type of fuel you can potentially hurt the car engine.

Regarding the problem you experienced with Memcached and the 503 error, It would be great if you could check the debug_log as those errors are logged so we can determine the cause of the problem.
I am running several instances using Memcached for different features (Page Cace. Object Cache, Database Cache) and I’ve had no issues regarding 503 errors. Since I am not seeing any support topic opened for this, it would be great if you could provide the information or reach out to us directly, as we are more than happy to assist you in identifying the problem.

Thanks!

It works – for a while, then just starts throwing 503 errors. Removing the plugin fixes the issue. It seems to be related to fastcgi connect errors :

[client 192.168.0.2:60744] AH01067: Failed to read FastCGI header
Connection reset by peer: [client 192.168.0.2:60744] AH01075: Error dispatching request to :

I’m running php_fpm via a socket and apache running mpm_event.

I was only trying memcached and your plugin because of the annoying “You should use a persistent object cache” message in the site health page.

Hello @steveatty

First of all, I am sorry it took me so long to reply back as I did not receive the notification for this.

Seeing the error you shared, the error means that when Apache was communicating with PHP-FPM, the PHP process did not respond properly. This is why you should have opened the support topic. This may be an annoying error, however, you pointed out that the problem is related to Memcached, so the obvious is that this is a Buggy PHP Extensions, and this may happen depending on the version. The solution is to remove and reinstall the proper version of the PHP extension and restart PHP.

Once again I am sorry for any inconvenience and I hope you will reconsider, and use W3 Total Cache again, now with proper instructions on the possible problems.

Thanks!

“Buggy” version of the memached extension? All installed from the stock repository. It’s moot as I’ve de-installed your plugin and memcached.