We are attempting to switch to this plugin. The main issue I’m finding is that it assumes a single blog install, not multisite. Therefore, it doesn’t work 100% correctly when a site-admin Network Activates this plugin. Options menus, under a Network Activation environment, should not appear on individual blogs and just the Network Dashboard settings menu. The available options are fairly harmless though except the bulk of our bloggers are not exactly tech-savvy, so I’m going to get to deal with lovely issues. Also, the .htaccess directives this plugin generates is wrong when multisite is enabled.
The other issue is that this plugin is still too heavy. The point at which caching plugins get loaded in WP is WAY too late, so plugin authors might as well load the entirety of WordPress at that point. This isn’t your fault. The only real fix is to have users modify wp-config.php and call the cache directly (it’s about the third PHP file that is loaded by WP and PHP has only consumed a few KB RAM at that point with no DB connection). PHP offers more refined control over program flow than .htaccess and optimized PHP can do a better job than Apache/nginx can with complex rulesets. Running ‘uptime’ with this plugin, I still get CPU loads from 0.98 to 1.82 with this plugin running. This is the only WordPress install on the box and the box only runs WordPress. At least this plugin isn’t as bad as W3 Total Disaster Cache where I was seeing ‘uptime’ numbers in excess of 4.57! WP Super Cache + Apache delivers RSS feeds at random times (unresolved, weird bug, still exists!) but hangs around the same CPU loads as this plugin (so far). I’m crossing my fingers for having no weird issues with this plugin.
- The topic ‘Not quite fully functional for multisite’ is closed to new replies.