[wp-trac] [WordPress Trac] #11399: clean_post_cache() generates enormous amounts of queries on sites with lots of pages, revisions or attachments

[WordPress Trac]

#11399: clean_post_cache() generates enormous amounts of queries on sites with lots
of pages, revisions or attachments
-------------------------------------------------+-------------------------
 Reporter:  Denis-de-Bernardy                    |       Owner:
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
Component:  Optimization                         |  Release
 Severity:  normal                               |     Version:  2.9
 Keywords:  dev-feedback has-patch needs-        |  Resolution:
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by nacin):

 Currently, ancestors are cached directly in the post object. This is
 really the only reason to look through the entire tree and invalidate
 caches. While revisions should never change, this would result with
 polluted data for their ancestors.

 There's a plan in #21309 to split ancestors into another cache bucket.
 This may go a long way to enabling us to drop this.

 Second, has anyone noticed that in wp_delete_post() and possibly
 elsewhere, we call clean_post_cache() on its children after
 clean_post_cache() would already have done that?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11399#comment:13>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software