Opened 14 years ago
Last modified 4 years ago
#11381 new defect (bug)
display_page_row() generates boat loads of needless queries
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Posts, Post Types | Keywords: | needs-patch |
Focuses: | performance, administration | Cc: |
Description
on sites with many static pages that are spread across multiple parents, display_page_row() triggers multitudes of calls to the db.
specifically, it's repeatedly calling get_pending_comments_num(). it's also calling get_editable_user_ids() and wp_dropdown_users(), both of which do not seem to cache their results in case they're used several times on the same page.
Attachments (2)
Change History (14)
#5
@
10 years ago
- Component changed from Optimization to Administration
- Focuses performance added
I think some of this is improved. get_pending_comments_num() still looks not so improved.
#6
@
10 years ago
- Component changed from Administration to Posts, Post Types
- Focuses administration added
#8
@
8 years ago
- Keywords needs-patch added; has-patch removed
- Milestone changed from Future Release to 4.4
get_users()
is still missing a cache
This ticket was mentioned in Slack in #core by sergey. View the logs.
8 years ago
Note: See
TracTickets for help on using
tickets.
a similar problem exists on the edit posts page, with _post_row() and inline_edit_row().
in particular, there are multiple calls to get_tags_to_edit(), in spite of the fact that the latter seem cached towards the beginning of the page.