In wpmu (not wp) the wp_load_alloptions function ignores autoload when selecting. This leads to massive waste. At the moment this query is returning over 1mb each time. Since this has been implemented (2.2 i think) the amount of data getting pulled out of my database has tripled.
The bulk of the data in the options table that is making this so painful seems to be magpie content that is pulled from the developer blogs or something. It is not used (for the most part) an just sits there.
A few questions to this end:
- is this an oversight?
- if not, why do this?
- can i disable the rss feeds that generate all of this data that i have no user for?
- if not whereabouts in the code might i comment out the functionality that updates this?
- if i alter the query in the wp_load_alloptions function to behave more like it does in wp (only selecting autoload = yes) does anyone foresee any nasty surprises in my future?
thank you in advance.