One of the facts which I’ve written about at length, is that while my home-computer ‘Phoenix’ has acted well as my Web-server, I am aiming to improve its performance as much as possible through caching, and through the daemon named ‘
memcached‘ specifically. I have a new plugin installed on my blogging engine, which connects to
memcached, and this plugin tries to cache a larger set of categories, of object-types that exist within the WordPress blogging engine.
One of the less-fortunate side-effects of this is, that every time, after I update my other plugins, there are malfunctions, due to WordPress not recognizing that the plugins in question have been updated to their new version.
There is a logical solution to this problem, which should work, which is to restart
memcached after each plugin-update. This should be harmless and flush the cache.
Again, a less-fortunate side-effect of this policy will be, that the site will seem a bit slow, after each plugin-update, and that indeed, I will not announce
memcached restarts anymore.
A fortunate side-effect of how much the new plugin caches is, that it seems to be improving the performance of the site more, than the old caching plugin did. It almost seems to have become possible, that WordPress is serving out the blog, while accessing the actual hard-drive infrequently.