[buddypress-trac] [BuddyPress] #4060: Improve performance of BP_Core_User::get_users()

[buddypress-trac at lists.automattic.com]

#4060: Improve performance of BP_Core_User::get_users()
-----------------------------------+-----------------------------
 Reporter:  shanebp                |       Owner:
     Type:  enhancement            |      Status:  new
 Priority:  normal                 |   Milestone:  Future Release
Component:  Members                |     Version:  1.2.9
 Severity:  critical               |  Resolution:
 Keywords:  1.7-early 2nd-opinion  |
-----------------------------------+-----------------------------

Comment (by shanebp):

 Boone - so your main reason for not moving last_activity to a new table is
 due to your aversion to creating a new table ?  Granted wp_bp_activity
 already has a date_recorded column that *is* indexed, but wp_bp_activity
 can also get very big.

 btw - I couldn't figure out how to implement your ideas above, so I
 decided to try the new table for last_activity approach. And got it
 working for last_activity, but it breaks too many other things, like
 search, due to the need for restructuring query logic.

 I'd be happy to track down  wherever user activity is recorded and fetched
 elsewhere in BP.
 I could deliver a list rather than a patch.

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