Database size increase

Hey Dave,

You could try disabling Live Traffic and then see if the database growth decreases. You still get all the security benefits.

-brian

Hi Brian,
thanks for this suggestion – I have disabled a few more things, jsut ran a scan and will check on the db size.
As shown on a few other posts. I tried the truncate table wp_wfHoover
–
Our host showed me this output and the wp_options.MYD and .MYI seems to large as does the
… mysql mysql 171M Feb 24 22:26 wp_options.MYD
… mysql 20M Feb 24 22:26 wp_options.MYI
… mysql 14M Feb 24 22:26 wp_wfHits.ibd
… mysql mysql 10M Feb 24 12:57 wp_wfFileMods.ibd
… mysql mysql 9.0M Feb 24 12:57 wp_wfConfig.ibd
… mysql 9.0M Feb 24 22:26 wp_wfLeechers.ibd

Is it ok to empty the wp_wfHits, wp_wfFileMods and wp_wfLeechers tables? (oops already done this and wordfence still seems ok – scan works).
I have Live Traffic disabled since the db growth was noticed (from less than 80MB pre-wordfence to 211MB) – I have increased our quota to 300 but this is a little unusual for a standard wp using minimal avada + woocommerce.

Any advice is appreciated – I do intend to go to the pro version btw ??
Regards,
Dave

wfHits stores all the hits in Live Traffic. Disable Live Traffic before clearing this. This may be the reason for growth if you have lots of traffic while LT is enabled. I usually leave it off unless I see server issues.
wfFileMods stores a list of the file we find during a scan. This can be cleared but not during a scan.
wp_wfLeechers is used to track visits by crawlers, humans, etc and is used in rate limiting. This can be cleared.

I would recommend deactivating wordfence before performing these operations in the database.

Hope this helps.

tim