So, as WP 2.6.1 has been released we should probably see a fair bit of ‘trac action’ and WPMU 2.6.1 on the way soon too.
However, I’m personally not going to be rushing into any upgrades from WPMU 2.6 based sites, there’s a lot more involved in upgrading WPMU rather than regular WP and if it doesn’t have great new features, important security fixes or serious performance tweaks… if it ‘aint broke, then don’t try to fix it!
Howabout you?
With your WPMU, are you a ‘cutting-edge’ Kevin or a ‘wait and see’ Wanda?
wait and see Wanda. As you said, if it ‘aint broke, then don’t try to fix it!
Cheers.
I’m a “wait and see Wanda” too. For http://thripp.com I’m planning on jumping from 1.5.1 (WP 2.5.1 equiv.) to WPMU 2.7 when it’s released. It’s easier that way, and I’ll try to change my hacks to the core to plugins in the interim.
Yep, we’re kinda tempted to wait for 2.7 too… 1.5.1 is really solid.
But just ‘Turbo’ on its own might persuade me to go for 2.6.1 when it comes out!
James; Do you think ‘Turbo’ would save you much bandwidth?
Merging and gzipping the JavaScript and CSS, and setting far-future HTTP expires headers, would be better than Turbo. The admin pages are too heavy now. I don’t think you can make those changes with a plugin unfortunately.
Turbo is purely a personal thing – I doubt it’ll do much for our servers but I’m starting to find it intolerable to be using backends without it!
Can’t comment much on http expire headers / gzip although wp-cache can do some of that, right?
@James: On the front end, but not on the back end unfortunately. WP-Cache’s gzipping isn’t useful because it does it on every page load which uses too much CPU power; WP Super Cache is what I use because it caches each gzipped page. It’s even faster than WP-Cache, but anything dynamic like hit counters (unless JavaScript), popular posts, etc. won’t be dynamic because it serves static HTML. The cache is invalidated / updated for new posts and comments, and every hour (configurable), and it’s WP-Cache only on the front-end for logged-in users, which is slightly slower but allows some dynamic content (like the Site Admin link; you don’t want that appearing to the general public, even if it goes nowhere).
Even WP Super Cache doesn’t touch CSS, JS, or the admin pages, though.
The admin pages are too slow… I’m making a simple write post panel that appears at the top of the home page of http://daytonastate.org blogs when users are logged in. Just title, body, tags, and category fields, and post or save as draft, with no fancy JavaScript or autosave to keep things quick.