Jim Boy
Well-known member
We've found out, the hard way, that in 1.3 forum_list cannot handle large number of users, unless we set our script memory limit to a higher figure.
In debug mode forum_list was consuming 140MB of RAM, even after turning off any suspect add-ons and all widgits. It looks as if the culprit is XenForo_Model_Session:repareSessionActivityFetchOptions(). Changing the amount of time that a user is online to one minute alleviated the issue and dramatically reduced memory usage. SQL call is below
Without any sort of limiting of the data retrieved, this will remain an issue. Of course it only happens when we are super busy, but that is exactly the time when we dont want it happening.
We will be migrating to 1.4 in about a month or so, depending on the stability of add-ons we require
In debug mode forum_list was consuming 140MB of RAM, even after turning off any suspect add-ons and all widgits. It looks as if the culprit is XenForo_Model_Session:repareSessionActivityFetchOptions(). Changing the amount of time that a user is online to one minute alleviated the issue and dramatically reduced memory usage. SQL call is below
Code:
[LIST=1]
[*]SELECT session_activity.*
,
user.*,
user_profile.*,
user_option.*
FROM xf_session_activity AS session_activity
LEFT JOIN xf_user AS user ON
(user.user_id = session_activity.user_id)
LEFT JOIN xf_user_profile AS user_profile ON
(user_profile.user_id = user.user_id)
LEFT JOIN xf_user_option AS user_option ON
(user_option.user_id = user.user_id)
WHERE (session_activity.view_date > 1411390264)
ORDER BY session_activity.view_date DESC
Run Time: 0.078202
Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
SIMPLEsession_activityrangeview_dateview_date4 9105Using where
SIMPLEusereq_refPRIMARYPRIMARY4bigfooty.session_activity.user_id1
SIMPLEuser_profileeq_refPRIMARYPRIMARY4bigfooty.user.user_id1
SIMPLEuser_optioneq_refPRIMARYPRIMARY4bigfooty.user.user_id1
[*]
[/LIST]
Without any sort of limiting of the data retrieved, this will remain an issue. Of course it only happens when we are super busy, but that is exactly the time when we dont want it happening.
We will be migrating to 1.4 in about a month or so, depending on the stability of add-ons we require