[buddypress-trac] [BuddyPress] #4076: Use transients for expensive activity queries

[buddypress-trac at lists.automattic.com]

#4076: Use transients for expensive activity queries
--------------------------+-----------------------------
 Reporter:  boonebgorges  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Activity      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+-----------------------------

Comment (by DJPaul):

 As we'd need to be able to clear these transients pretty easily, and if
 you build the keys from a range of variables, we're probably limited to
 the sort of caches that you've bulleted pointed. Things like searching +
 pagination + max variables would be really challenging to clear when one
 part of that changes. I think it makes sense and we will end up with a
 model for anyone implementing Activity into their plugin to copy.

 You want to have this as a kind of level of template loop caching, rather
 than at a lower level in bp_activity_get()? If doing that it seems to me
 that the transient caching would better go in BP_Activity_Template's
 constructor. It would also capture anyone creating a BP_Activity_Template
 object directly, or re-implementing bp_has_activities(), for whatever
 unusual reason.

 What would happen to existing wp_cache in bp_activity_get()?

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4076#comment:1>
BuddyPress <http://buddypress.org/>
BuddyPress