[wp-trac] [WordPress Trac] #32068: Excessive overhead in widgets.php on large site

[WordPress Trac]

#32068: Excessive overhead in widgets.php on large site
----------------------------+------------------------------
 Reporter:  ronnieg         |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  4.1
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by boonebgorges):

 widgets.php has the Pages widget, which contains a dropdown of pages.
 Options > Reading contains a dropdown of pages for the "front page"
 option. Generating this dropdown means building the page tree. In some of
 these cases we might consider building the dropdown asynchronously, or
 only partially, or something like that.

 > However, it does beg the question as to why every page / post has to be
 accessed all at once at the beginning in the Pages / All Pages function,
 instead of using a paginated approach, and just accessing the next 20 to
 however many it needs for a particular display page.

 When paginated page results are displayed in a way that respects page
 hierarchy, the hierarchy more or less has to be loaded in full before it
 can be decided which results belong on a given page. If you have a
 structure like this

 A
   AA
      AAA
   AB
      ABB
   AC
 B
 C
   CA
   CB
      CBA
      CBB
      CBC

 the second page of results when per_page = 5 should contain AC, B, C, CA,
 and CB. There's no way to calculate this without knowing what the whole
 tree looks like. See #15459.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32068#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform