Title: Database too large
Last modified: May 14, 2025

---

# Database too large

 *  Resolved [damo105](https://wordpress.org/support/users/damo105/)
 * (@damo105)
 * [1 year ago](https://wordpress.org/support/topic/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:**
    2.   - 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?
    3.  **`spbc_vulnerabilities` Option in `wp_options`:**
    4.   - 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?
    5.  **Log Retention for Security Plugin Tables (e.g., `wp_spbc_firewall_data_v4`,`
        spbc_scan_results`):**
    6.   - 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?
    7.  **Logging of Whitelisted Administrator Activity:**
    8.   - 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.
    9.  **(Optional, if still concerned) `cleantalk_sfw_update_queue` Option:**
    10.  - 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,”

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [katereji](https://wordpress.org/support/users/katereji/)
 * (@katereji)
 * [1 year ago](https://wordpress.org/support/topic/database-too-large/#post-18464945)
 * Hello.
 * Thank you for your questions. I have created the task for our developers and 
   they will prepare detailed answer for you. Please give us a couple of days to
   get back to you.
 *  Plugin Support [eugenecleantalk](https://wordpress.org/support/users/eugenecleantalk/)
 * (@eugenecleantalk)
 * [1 year ago](https://wordpress.org/support/topic/database-too-large/#post-18471492)
 * We thank you for your questions. Here are our answers:
    1. This table depends only on the number of entries in your personal lists. Only
       by the composition of these entries you can change the size of the table. The“
       Use CleanTalk database of dangerous IP addresses” option has no effect and applies
       to the Security by CleanTalk plugin. The option “Logs are kept up to 45 days”
       also has no effect, because it defines the period of time logs are kept on our
       servers.
    2. The size of the spbc_vulnerabilities depends on the number of plugins on your
       site. Accordingly, you can reduce the size by removing unnecessary plugins. 
       You can set autoload = ‘no’ for this option to optimize it.
    3. The wp_spbc_firewall_data_v4 table stores the list of networks for Security 
       FireWall, updated once a day. The presence of entries in this table is determined
       by the “Use CleanTalk database of dangerous IP addresses” option. The spbc_scan_results
       table stores the results of the Malware Scanner. The more files on the server,
       the larger this table is. The “Logs are kept up to 45 days” option has no effect
       on the size of the tables on your site.
    4. Our plugin is designed in such a way that it logs all actions of all users. 
       Traffic Control is a different module, its “Ignore logged in users” option does
       not affect logging of actions in the admin area. Unfortunately, at the moment
       there is no way to disable these logs or configure exceptions for whitelisted
       IPs. We can think about this functionality. Could you please clarify what the
       size of these logs is to understand what kind of gain we can get?
    5. Yes, the size you mentioned is typical. For optimization you can set autoload
       = ‘no’ for this option.
 * We’ll be waiting for your feedback.
 *  Plugin Support [eugenecleantalk](https://wordpress.org/support/users/eugenecleantalk/)
 * (@eugenecleantalk)
 * [1 year ago](https://wordpress.org/support/topic/database-too-large/#post-18477887)
 * Hello.
 * We haven’t heard back from you in a few days, so I’m going to mark this topic
   as “resolved”. If you have any further questions, you can start a new topic or
   contact us via our private Ticket System: [https://cleantalk.org/my/support/open](https://cleantalk.org/my/support/open).

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Database too large’ is closed to new replies.

 * ![](https://ps.w.org/security-malware-firewall/assets/icon-256x256.gif?rev=3518712)
 * [Security Plugin, Firewall & Malware Scanner with Auto Removal](https://wordpress.org/plugins/security-malware-firewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/security-malware-firewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/security-malware-firewall/)
 * [Active Topics](https://wordpress.org/support/plugin/security-malware-firewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/security-malware-firewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/security-malware-firewall/reviews/)

## Tags

 * [database](https://wordpress.org/support/topic-tag/database/)

 * 4 replies
 * 3 participants
 * Last reply from: [eugenecleantalk](https://wordpress.org/support/users/eugenecleantalk/)
 * Last activity: [1 year ago](https://wordpress.org/support/topic/database-too-large/#post-18477887)
 * Status: resolved