Basic Setup is:
- 2 load balanced servers on the front end
- memcache enabled for backend
Based on some other threads out there we've:
- Increased the max_heap_table_size setting to 500MB
- Altered the xf_session_activity table:
- ALTER TABLE xf_session_activity
- DROP PRIMARY KEY,
ADD PRIMARY KEY (user_id, unique_key) USING BTREE;
The common issue here seems to have been with session related tables as they can grow rapidly. Possibly storing session info in memcache may help?
Session tables like xf_session_activity, right now the 8469 rows in it, does that mean the site thinks there's that many users on the site right now or can bot traffic get caught in the mix here?
Is there anything else I should be doing to aid the database performance that the other sites with busy forums like DigitalPoint have done?
We are testing running deferred.php as a true cron on one of our smaller forums, so far it seems good but we haven't implemented it yet on our busier forum as it feels like there's been too many moving parts the last few days.
Any help is greatly appreciated, we're unsure where to turn at this point.