MultiNetwork compatibility?

I’m switching from Redis Object Cache, mainly because of the compatibility issues with WP Multi Network. I have several sub-networks that have to be maintained separately, but since the ROC plugin can have only one object cache, I had all kinds of wierd behavior. The object cache on the main network did not seem shared with other sub-networks, as I assign more blogs to sub-networks and keep less blogs in the main network. The metric got decreased to nearly zero, which I guess means there is nothing to cache for. i.e. sub-network contents were not object cached.

For Docket Cache, I’ve tested it for a few hours, and it seems like, whether I activate the plugin in sub-networks or not, the main network cache is working. The sub-network’s cache disk is nearly fixed at small amount (20~30M), while the main network’s cach disk goes with 200~400M on average. I believe the sub-network’s 20~30M is only for the sub-network’s main site.

I set the cache disk limit to 2G for all main- and sub-networks, and also used your code to create RAM cache (not sure if it worked though, because it looks like to create only 1 RAM disk). I have a dedicated server with plenty of hardware resources so it is no big deal, as long as the cache works.

I wonder if what I see is normal, or if I have to change any settings for sub-networks. My ideal case is separate cache for each sub-network, and each can have separate RAM disk.

After a few hours, I already have cache files as ‘199000 / 200000’ for the main network. One way to handle it is, I guess, to increase the limit in your code, but this won’t help me to create multiple object cache files for each sub-network.

Overall, the idea seems great in that object cache files are created in PHP format, which is the fastest possible option for PHP servers, and w/ RAM disk option, if all PHP converted object/op cache files are stored in RAM disk, it isn’t that different from Redis. In comparison to PHP-Redis, I do not feel that much difference, though this ‘feeling’ should be verified reasonable benchmarks. But, as long as it works with my multi-network, I have no reason to go back to Redis.