July 18, 2015
Reduce wordfence plugin’s load on MySQL database
Wordfence creates huge loads on MySQL database (around 90+MB in just a week)
HOW TO REDUCE THIS LOAD
1) Disable live-site activity monitoring when there is no evidence of an attack
Wordfence > Options
Uncheck “Enable Live Traffic View.”
NOTE: If Live Traffic View had been enabled in the past, go to bottom of the page and check “Delete Wordfence tables and data on deactivation?”
NOTE: I tried this but it did not work. Database is still very large.
NOTE: On a regular basis, go to Wordfence > Live Traffic and view the attempted and successful Logins tab. You can permanently block any IP addresses that are trying to login to your account that are obvious hack attempts.
2) Empty wf_leechers
3) IF THIS DOESN’T WORK, DELETE WORDFENCE AND ACTIVATE AGAIN
Under Plugins, deactivate and delete Wordfence. This does NOT, however, delete all the Wordfence tables in the database. You need to go to the database and drop all wf tables (around 15 or so of them).
NOTE: I used wp-rocket and found it works well, so I re-added Wordfence, but unfortunately the database went haywire and 500 errors have returned. I’ve deleted wordfence again.
NOTE: When reinstalling the following usernames can be blocked by default: bc-sekaran,sanjeev sabhlok,sabhlok-2,admin,wpengine,webmaster,www,sabhlok-2-2,sabhlokcity,sabhlok-2,admin,www.sabhlokcity.com,aa
ACTIVATE BY REINSTALLING A FRESH VERSION. A new version takes around 1 month to clog the SQL database.