Thanks for the reply, it's appreciated.
The 1.9 and 1.12 installs are running on the same machine, and are not
receiving any traffic other than my testing. 1.9 is pointing to a production
DB instance, both are pointing to the same MySQL server, but I changed the
wgProxyKey for both installs so they don't hit the live memcached, could 1.9
be getting some cached data from the production DB to make it perform
I'll take a look into the extra queries, they could be coming from our
customizations and extensions.
This query occassionally takes a long time to execute, not sure why:
SELECT /* Parser::replaceLinkHolders */ page_id, page_namespace,
page_title, page_is_redirect FROM `page` WHERE (page_namespace=0 AND
page_title IN('Study-Better', 'Have-Fun-While-Studying',
I repaired all
of the tables in the 1.12 database
Are you using MyISAM? If so, why? MediaWiki isn't really designed
for it at all; it uses InnoDB-specific features like primary key
No idea! Is it possible because we originally created this DB with a MW 1.3
install, that not all the tables have been converted? It looks like our
`archive` table is MyISAM, but in the new MW installs, it's InnoDB. Should
we switch them all over to be Inno?
Why don't you use maintenance/update.php from a shell? It's almost
certain to be more reliable.
Cool, I didn't know this existed. I'll use this next time.