Update on Wordpress Autoload Option Experimentation

/update-on-wordpress-autoload-option-experimentation 2008-04-21T11:12:32+01:00

Well, after running with ALL options in the wp_options table set to no for autoload for about 3 days, I can say it doesn't really make much difference. If anything, there may be a slight decrease in performance, but nothing broke that I could see, and there really wasn't a significant difference in memory usage either.

I've reverted back to the original settings. I'll have to dabble with the Wordpress code itself to see if there are any global variables that don't really need to be global at all. I've done some initial investigation and there are tons of stuff loaded into the global variable scope that probably shouldn't be, for example - all the smilies (abbreviations AND images), month and day abbreviations and the whole rewrite rules table.

I've searched the WP mailing list achives and it seems the last time memory usage was actively discussed was way back in 2006. Is it really worth digging this up again when it appears very little was actually done about it?

Come to think of it, maybe it'll be quicker just to try switching to another platform - Habari looks promising as it seems to be designed with performance in mind.

Anyone had any experience with Habari and migrating from Wordpress to Habari? Any feedback good or bad would be great.

Copyright © 2005 - 2018 Colin Seymour All rights reserved. Privacy Policy.
Check out the feed if you do the RSS/Atom thing.