Database too large

Hi CleanTalk Support,

I’m using your Anti-Spam and Security plugins on my WordPress website and I’m working on optimizing my database performance. I have a few questions about how your plugins store data and how I can manage it:

1. Managing wp_cleantalk_sfw_personal Table Size:
   • My wp_cleantalk_sfw_personal table is currently quite large (around [mention its current size, e.g., 39.1 MB]). I have the “Use CleanTalk database of dangerous IP addresses” setting enabled in my Cloud Dashboard.
   • Besides this main list of dangerous IPs, what other data (e.g., SFW activity logs, local copies of personal lists) contributes to this table’s size on my local WordPress database?
   • How is the growth of this specific table managed or pruned, particularly in relation to the general “Logs are kept up to 45 days” setting? Are there specific actions I can take to reduce its size without disabling the main SFW list from your cloud?
2. spbc_vulnerabilities Option in wp_options:
   • The spbc_vulnerabilities option in my wp_options table is over 58KB and is set to autoload = 'auto' (or yes).
   • For optimal site performance (reducing TTFB), does this option absolutely need to be autoloaded on every page load for your Security plugin to provide effective real-time protection?
   • Or, can its autoload flag be safely changed to 'no' (so it’s only loaded by the plugin when specifically needed, like in the admin area or during scans)?
   • Are there any settings to manage the amount or scope of vulnerability data stored in this specific option?
3. Log Retention for Security Plugin Tables (e.g., wp_spbc_firewall_data_v4, spbc_scan_results):
   • I found a general setting that says “Logs are kept up to 45 days.” Could you please clarify if this 45-day retention period applies to the security firewall logs (stored in tables like wp_spbc_firewall_data_v4), malware scan results (in spbc_scan_results), and other logs generated by the Security by CleanTalk plugin?
   • Is it possible to set a shorter retention period than 45 days for these specific security logs, either globally through my CleanTalk Cloud Dashboard or within the WordPress plugin settings, to help manage database size?
4. Logging of Whitelisted Administrator Activity:
   • My whitelisted administrator IP address (e.g., 203.56.128.15) generates many “Passed” log entries when I navigate the WordPress admin area (e.g., viewing plugin settings pages).
   • While I want to log actual blocked threats, is there a way to reduce or disable the logging of these routine, permitted “Passed” page views specifically for whitelisted administrator IPs? I have enabled “Ignore logged in users” under Traffic Control in the Security plugin, but still observe other admin activity being logged.
5. (Optional, if still concerned) cleantalk_sfw_update_queue Option:
   • The cleantalk_sfw_update_queue option in wp_options is over 43KB and autoloads. Is this a typical size for this option, and is there any way to manage or optimize it?

Any guidance you can provide on these points to help me better manage the database footprint of your plugins while maintaining good security would be greatly appreciated.

Thank you,”