What are the possible bad consequences of enabling your cache plugin on several sub-sites under a multisite WP installation? Would it totally break?
The technique of DB caching seems superior to page caching but W3 Total Cache (which has that) is just WAY too complicated and some of my pages would not refresh at all, even with ctrl-F5. So I’m wanting yours to work since Caching is one of those system utilities that should just work quietly in the background so we humans can get on with OUR work and not babysit it.
I have enabled it on my Multisite http://articles.architectjaved.com and there have been no problems with it…
The speedup from DB Cache Reloaded (Fix) is likely small but worth a try after Ivan has time to incorporate the fixes that make the installation and activation easier.
Thanks for replying Fredrick. I abandoned DB-Cache-Reloaded, not sure why now.
My two main production sites chowstalker.com and dessertstalker.com are using QuickCache which seems to have helped with the “First Byte Time”, but webpagetest.org still gives me an “F” for “Cache Static Content” (which I thought was the main purpose of a caching plugin). But they are chugging along fine with no one complaining of downtime or slowness. They have issues with an inefficient, db-heavy plugin so will eventually be replaced with a new design to take advantage of the built in features of WP3.x, so I’m not worried about them until something breaks.
For future projects I’d like to use something more robust (like W3 Total Cache or WP Super Cache), but I’m afraid I will need a university course to figure out how to make them work. Does W3TC work with out-of-the-box, default settings so I can just activate it and let it work in safe (but probably not optimal) mode?
It should work out of the box and if it doesn’t I would like to work with you to learn why, so please submit a bug submission form when you try it again if you have issue working through the installation instructions.
I will install W3TC on a test site soon and let you know how it works out of the box. I probably just didn’t think it through back then since I was sort of in panic mode when my site was “down”. But I know more of the terminology now and it should make more sense.
In case I need it, are you referring to the bug submission form here: http://wordpress.org/tags/w3-total-cache ?
Thanks for your support!
> Ron Strilaef
Adding something like the following will enable browser side caching of static content
Frederick: I wanted to ask someone about Minify, and you’ll surely know. The question is, whether it either forces or allows for combining the .js and/or .css files so they’re all transmitted at once? I know the main function of Minify sometimes causes problems, but this shouldn’t, while it would still provide a speed benefit as there’d be ideally only one JS and one CSS request.
Ron and Paul:
Paul’s .htaccess tells the browser to cache the files for 365 days (31 536 000 seconds). I wouldn’t personally consider anything longer than a month (2 592 000 seconds) and would most likely choose either 1 or 2 weeks (604 800 or 1 209 600 seconds). That should provide a speed benefit while also making sure there’ll be no rare conditions where someone keeps seeing older versions of updated content for ages. I think Google serves the forever-unchanging jQuery files they host with a 2 week expiration date.
In auto mode, W3TC will try to make a single file. In manual mode the same is true however manual mode is the only way to exclude files or add 3rd party files. Minify is one of the best performance wins for the client-side of things.
Browser cache is another huge performance win and W3TC can manage the policies for your entire site and allow you to remove any existing rules (policies).
Thanks for the answer Frederick, that sounds good. I might give W3TC another go if increasing user amounts on our site prompt us to look for speed optimization. While using W3TC some two years ago I ran into a sitewide white screen of death that required FTP removal of the plugin to resolve. Hopefully during these two years the plugin has learned to avoid or gracefully overcome more of these situations.
Right now I’m pretty happy with WPSC. The only issues so far are the admin bar’s Delete Cache button that sometimes shows and sometimes doesn’t, possibly due to a plugin conflict, and the fact that garbage collection stopped completely when set to run first at 00:00 and then hourly. It runs like a clock now when it’s set to run at a specified interval (300 seconds). Site is fast and the plugin causes no extra maintenance besides having to keep a browser tab open displaying the plugin’s clear cache option while developing. Minifying and combining the .js and .css files could make things faster especially for mobile connections, but as setting that up takes time and can lead to unexpected problems, it’s not yet among the immediate priorities.
Ideally I’d just add a Minify solution to my current setup and manually choose for it to combine the files that are not under development. However, WP Minify has several unsolved critical issues raised during the last month and the other plugin I know of, Minify, is so new that it has only one rating and an unsolved critical issue. W3TC is tried and tested, but is quite a mammoth to install just for the Minify.
- The topic ‘DB Cache Reloaded Fix for Multisite’ is closed to new replies.