Changes between Version 4 and Version 5 of Ticket #4060, comment 6
- Timestamp:
- 03/12/2012 01:27:39 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4060, comment 6
v4 v5 1 1 boonegorges - seems like we're having a bit of an apples/oranges discussion. 2 2 3 For us, the issue isn't joining on wp_bp_activity - it's the left join on wp_usermeta in BP_Core_User -> get_users();3 For us, the main issue isn't joining on wp_bp_activity - it's the left join on wp_usermeta in BP_Core_User -> get_users(); 4 4 For example, look at the Rows_examined in this snip from todays slow log: 5 5 … … 10 10 }}} 11 11 12 13 Selects on wp_bp_activity never shows up in our slow-log. 14 But get_users with the left join does frequently - and other simple queries start stacking up behind it. 15 16 17 18 ( I've looked at #4045. We only have ~250k rows in that table. ) 12 And other simple queries start stacking up behind it. 19 13 20 14 Adding only as many rows as there are members is exactly the problem with using wp_usermeta to store 'last_activity' time-stamp.