Twenty Ten makes too many queries for index pages

[demetris]

The testing environment is nothing fancy or excessive:

• Current trunk (r14186)
• Default widgets (Search, Categories, Meta)
• Four plugins (Markdown Extra, SQL Monitor, WP Console, WP-Syntax)
• Ten (10) posts per index page

In that humble setup, Twenty Ten makes thirty-four (34) queries to put together the home page, archive pages, etc.

(If I replace wp_nav_menu with wp_page_menu, the number goes down to 31.)

For reference, the Hybrid theme (with the same widgets) needs 11 queries for the same job. Kubrick, if I remember correctly, used something in that area too, 10 or 11 queries.

I only have the vaguest idea of where this might be coming from, so I’ll leave the diagnosis to the experts, but over 30 queries for index pages in a default install seems too much to me.

I can top you with 62 queries for my front page.

Most of the queries are related to Taxonomy data loading. What we'd benefit from here is a mass-loading query, something which loads all the taxonomy data for a set of post_id's into the memory cache with a single query.

I think there are some functions which are also skipping potential cached data, as i'm seeing a few queries repeated (some by function1, which calls function2, which then makes the same query)

WP 2.9.2 stable with Default Kubrick Theme uses more than 10-11 queries for the home (index) page, in my experience. Even if no plugins are used. I think queries are more than 20, in fact...

Still, over 30 for WP 3 and new default theme seems a bit too much, maybe...

From a quick exploration of the taxonomy code, it looks like results are cached, but the cache is never checked in functions like wp_get_object_terms(). Looking at a decent way to remedy this now.

The removal of Twenty Ten’s custom taxonomy functions in r14384 brings the queries for index pages from 34 down to 12. So, issue fixed for Twenty Ten.

Since beaulebens is looking at the more general issue, I’m leaving the ticket open for now.

The other issue is menus, but we'll be handling that elsewhere (hopefully).

Closing this one as fixed then.

Is there another ticket for beaulebens to work in?