[wp-trac] [WordPress Trac] #16927: Don't use XHR to load portions of Dashboard that are "hot" in the cache

[WordPress Trac]

#16927: Don't use XHR to load portions of Dashboard that are "hot" in the cache
-----------------------------+--------------------------
 Reporter:  markjaquith      |       Owner:  markjaquith
     Type:  task (blessed)   |      Status:  reopened
 Priority:  normal           |   Milestone:  3.2
Component:  Performance      |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |
-----------------------------+--------------------------

Comment (by nacin):

 I'm not comfortable loading 30.3MB -- with server configurations and a few
 plugins, that goes above 32MB very easily. We either need a second layer
 of caching to avoid loading SimplePie on the dashboard, or we need to ask
 for more memory on the dashboard.

 I don't know which is easier. Second layer of caching might not be
 difficult to bake into the widget caching function, but I also know that
 trying to add transient caching drove both Mark and I mad initially.

 Asking for more memory is easy, but that's actually uncharted territory.
 We currently only bump the memory limit to WP_MEMORY_LIMIT or
 WP_MAX_MEMORY_LIMIT -- we want something in between, which means we need
 to check it against both of those constants. Given the pedanticism in
 #14889, introducing a middle-ground, hard-coded value of, say, 48MB might
 mean we need to revisit our memory comparison handling.

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