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

buddypress-trac at lists.automattic.com buddypress-trac at lists.automattic.com
Fri Mar 16 18:47:02 UTC 2012

#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 boonebgorges):

 > 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.

 More or less. All things being equal, we should avoid creating new tables.
 That's especially true in this case, since we literally already have a
 table devoted to recording *activity* items. It's true that size is a
 concern, but keep in mind that only a single last_activity item would be
 recorded at any time for a given member. So in a community with, say,
 10,000 users, an "average" size activity table may have 500,000 rows (50
 per user), but my proposal would only add 10,000 rows. That said, there is
 no question that activity query performance must be improved before my
 proposal can be seriously considered; see #4045.

 > 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.

 Any little bit is helpful. Thanks :)

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

More information about the buddypress-trac mailing list