[wp-trac] [WordPress Trac] #32068: Excessive overhead in widgets.php on large site
WordPress Trac
noreply at wordpress.org
Thu Apr 23 04:20:39 UTC 2015
#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 ronnieg):
Replying to [comment:6 boonebgorges]:
In some of these cases we might consider building the dropdown
asynchronously, or only partially, or something like that. ...etc...
That seems to be exactly what the plugin "Pages Tree View" does. It
displays only the pages at the root level at first, and only opens child
pages of a selected root page as required, when the parent page is
clicked, and then only for one child level at a time, and so on, not every
page at all levels at once.
This "on demand / drill down" process makes a lot more sense to me, both
functionally and performance wise. It also encourages and rewards a well
structured page hierarchy design and implementation, when there are no
more than a dozen or so main pages at the root level, and no more than a
few dozen or so child pages under each major parent page. In the case of
my 6000+ page site, I can drill down to the exact page I am looking for in
seconds, with no more than 2-3 clicks.
All this perceived need for every page all at once is based on the
assumption that every page in the hierarchy will need to be displayed,
when from a user/admin standpoint, I am generally only interested in and
working on a very small subset at any one point in time, so I am happy to
be able to "drill down" into very specific branches of the hierarchy as I
see fit and need. That's why the "Pages Tree View" plugin works so well
for me and my clients, even though Pages / All Pages fails due to
excessive overhead, combined with the very reasonable page load time
limits dictated by my hosting service, so they can support good page load
and response times for all of their customers.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32068#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list