[buddypress-trac] [BuddyPress Trac] #1332: Caching issues with profile data when using a persistent cache

[buddypress-trac]

#1332: Caching issues with profile data when using a persistent cache
--------------------------+---------------------
 Reporter:  swinton       |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  major         |   Milestone:  2.0
Component:  XProfile      |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by boonebgorges):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I've made a fairly thorough sweep of the queries made in the xprofile
 query classes. I've added support for persistent caching, along with the
 relevant logic for invalidation, in a number of critical places. While
 there are still a number of places where queries are not cached, I think
 I've gotten most of the queries that are run most frequently, and are most
 likely to cause performance issues at scale.

 There are a few remaining spots in the component that could benefit from
 some caching. In some of these cases (like the case of the 'fields' query
 in BP_XProfile_Group::get()) it'd take fairly significant refactoring and
 a complex caching/invalidation schema to be sensitive to all relevant
 parameters. In other cases, the queries are called so infrequently that
 the performance benefits would be minimal.

 I think I've added enough to justify marking this ticket as resolved, at
 least for the milestone. If problems arise, or anyone spots more places
 throughout xprofile that could benefit from object caching of some sort,
 please open a new ticket with details.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/1332#comment:20>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac