While trying to debug my server and finding out why it's so slow (empty atahualpa page needs 1.7 seconds to generate .... however only around 20% of CPU use, and plenty RAM Free) even though I have mysql and apache tuned for high performance (mysql mylare.cnf, xcache php accelerator, running wp-supercache-plus in full on mode...)

I see on my server status page several calls to old images from atahualpa 3.2 theme folder - which has long ago been deleted from my server....

They take quite a lot of time and I assume that maybe these calls are responsible for the slow loading of my page (most users won't notice as they get served static pages). I have around 2000 unique visits each day, and 15 minute CPU load maxes out at around 0.3-0.5 during the evening, while being well below 0.2 the rest of the day, plenty of free ram too....

Today I activated mod_server-status and I noticed that quite often calls are taking up to 2000ms CPU times for old images of atahualpa theme, based in folders that don't exist any more....

like this (sorry formattting broken):
Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request
0-0 7924 0/3/68 _ 2.53 47 2160 0.0 0.00 1.74 91.33.85.10 openmtbmap.org GET /wp-content/themes/atahualpa.3.2/atahualpa/images/sticky.gi


Is it possible that there are problems with atahualpa rewriting the database after bumping up the theme version? (since 3.2 I have allways updated)

see my server-status here (is this a security risk to leave this open? - link obstructed so no crawler follows it)
http:// xxx 77.236.97.248 xxx /server-status

You may have static page copies created by WP Super Cache that still reference old images?

No I thought about that and deletet the complete cache folder (already quite often) -- with 342 I still used wp supercache. Since 3.4.3 I use wp supercache plus and had to delete all cache files (on top I often switched between half on (xcache only) and full on (xcache and disk cache) mode - and on each change cache gets deleted.

However there might be residues in the mysql database - however I don't know in which table they are....

I simply do note that those calls to nonexistant files take a lot of time.

Would these 2 plugins help:

Debug Queries http://wordpress.org/extend/plugins/debug-queries/
Debug Objects http://wordpress.org/extend/plugins/debug-objects/

I already used debug_queries from while to while, but neither (also debug_objects) helped me to find out why the call to old objects happens.....

Only clean database and wordpress new install would help....

Except for that slow call (adds 2 seconds) if it happens (not on all posts/pages) it's qtranslate that really slows down pageloadtime. Pageloadtimes are like the following:

fresh wordpress install, standard theme: 0.1 second
imported posts/pages and activated all plugins I use except qtranslate: 0.3-0.5 seconds (the main slowdown is not the plugins but the imported posts/pages/comments)
activated atahualpa: 0.7-2.5 seconds
activated atahualpa and qtranslate 1.7-5 seconds.

again fresh install/fresh database and imported posts/pages
default theme and all plugins incl. qtranslate activated: 0.6-3.5 seconds

So essentially qtranslate and atahualpa don't play well together at all.

The slowdown because of requests to inexistant pictures is quite annoying nevertheless.

If the call to inexistant files does not happen, my old install with old database (optimized) is as quick as the new test installations.

If you want to check the Atahualpa options to see if there are links to old folders, try this.

1) Use the code described here (http://forum.bytesforall.com/showpos...95&postcount=5) and do the export. This will give you an file of the Atahualpa options.
2) Examine the file for links to the old file structure and change them.