What a MESS – Just cleand up 200MB from WP Options Table!!!

  • This is what happens when plugins are poorly written, my website was causing large spikes on CPU and RAM consumption, than I noticed mySQL was struggling although I have a really decent VPS.
    Decided to check things out… Immediately noticed something strange, my WP database was 270MB!!!
    Further investigation, top table in size was the options, further investigation, thousands of records with option name ctf_!_#xxxxxxxx, had to delete them all from the DB… now everything is back to normal!
    This plugin has been active for at least 1 year … clearly there is no cleaning up configured to prevent that DB grows to a huge size.

Viewing 1 replies (of 1 total)
  • Plugin Author Craig at Smash Balloon

    (@craig-at-smash-balloon)

    Hey brunocerq,

    Sorry about the database issue and confusion here!

    This is due to how our plugin allows you to display hashtag feeds that have tweets that are older than 7 days. Twitter only provides tweets for hashtag feeds that have been made within the last 7 days. To work around this, we have a “persistent cache” feature that saves them indefinitely.

    Each feed creates a record in your database to add up to 150 tweets that can be retrieved whenever they are needed. As far as we know this is a unique feature of our plugin.

    This feature can be disabled on the “Customize” tab using the setting “Persistent cache enabled by default”. You can also clear the persistent cache any time using the button that is by this setting.

    We don’t put a limit on how many feeds are created. Do you happen to have a large number of hashtag feeds on your site? This would explain why there was so much data added to your wp_options table. The plugin also does not clear any of this data on its own to allow the site owner to decide whether or not they want to clear feeds stored in the database.

    I do see how this can be better communicated and we just made plans to alert the site owner somehow if there are a large number of persistent caches stored in the database. That way they don’t have to find out when their site slows down or has RAM issues like you are experiencing!

    We do apologize for the frustration this caused. Let me know if you have any questions of any more feedback.

    Thanks,

    Craig

Viewing 1 replies (of 1 total)
  • The topic ‘What a MESS – Just cleand up 200MB from WP Options Table!!!’ is closed to new replies.