[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:  accepted
 Priority:  normal                  |   Milestone:  3.2
Component:  Performance             |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |
------------------------------------+--------------------------

Comment (by nacin):

 In principle I agree with Mark that we should cache the whole output. But
 after looking at it, I'm not sure.

 By caching final output, we end up with potentially staggered caches. The
 feeds are cached for 12 hours in a transient. If we cache the output on
 top of that, we can't cache it for long (Mark's patch makes it under a
 half-hour), or we could end up with a significant overlap that causes the
 data to be even more out of date than 12 hours.

 We need this cache to be as hot as possible for it to be a good impact on
 perceptive speed. The dashboard really isn't visited that often. Perhaps
 on login, when the cache has the least chance of being hot.

 It's a trade-off: The bit of time it takes to process the data of the feed
 is worth it when being able to hold the feed in cache for much longer. So
 I'd rather return to using wp_dashboard_cached_rss_widget(). This also
 prevents a number of widget args from busting the cache (only number of
 items, really).

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