huge table size wp_wfknownfilelist

Hi @ahawad, thanks for getting in touch.

wfknownfilelist should be truncated at the start of new scans. If you visit Wordfence > Tools > Diagnostics > MySQL, are your privileges to INSERT, UPDATE, TRUNCATE etc. here reporting back as OK?

One other check you could run is looking at the contents of that table, starting a new scan, and see if you are noticing any change/improvement at all. Are you noticing your scans are starting and completing successfully?

Thanks,

Peter.

ok, the wfknownfilelist table went down to 9MB.

Another table wp_wffilemods is 26+MB now… is it safe to empty?

Hi @ahawad,

wp_wffilemods should also get truncated when starting a scan. It should be safe to empty as it’s meant to happen next time a scan runs, but the size doesn’t particularly concern me. If you’re not seeing this clear, or constantly growing in size, I’d enable error logs and see if anything comes up during a scan. It might be good to check if the rows reset to 0 right when starting a scan and then increase again, and end about the same amounts, or if it only adds on.

Thanks again,

Peter.