• Resolved oriver

    (@oriver)


    Hi,

    I was made aware by my host server that my SQL databases were becoming huge.

    Part of this were the following tables:
    popularpostssummary
    popularpostsdata
    popularpoststransients

    I’ve emptied cache and cleared all data, while the settings I’ve put at:

    Log views from: Visitors Only
    Log limit keep data for: 7 days
    Ajaxify widget: enabled
    Data caching: enabled
    Refresh cache every: 5 minutes
    Data sampling: enabled
    Sample rate: 10

    Should this help keep the SQL low in the future? We haven’t as yet launched, but the tables became huge (this was prior to changing the settings) and so I wanted to make sure that when we launch we don’t compromise performance, while still having the popular posts regularly update.

    Thanks in advance for any help.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Hector Cabrera

    (@hcabrera)

    Hi @oriver,

    Yep, that should work.

    Note though that popularpoststransients is not a table created by WordPress Popular Posts. The only tables created by WPP are the first two (“summary” and “data”). Was that a typo?

    I wanted to make sure that when we launch we don’t compromise performance (…)

    You may have read this already but if not then it might be a good idea checking it out before launch: Performance Suggestions and Recommendations.

    Thread Starter oriver

    (@oriver)

    Hi @hcabrera

    Thank you for your help.

    No that wasn’t a typo. That’s a bit suspicious then, will take a backup and delete. Thank you again

    Plugin Author Hector Cabrera

    (@hcabrera)

    No that wasn’t a typo. That’s a bit suspicious then, will take a backup and delete.

    Don’t worry about it. As it happens I was working on the plugin earlier today and saw that there was indeed a time when WPP created that database table on first activation. Later on I determined that it wasn’t useful so I removed it from the plugin shortly after.

    It’s been a long time since then so I had completely forgotten about it 😛 Sorry about that!

    Thread Starter oriver

    (@oriver)

    Hi @hcabrera

    Oh that’s great, so I should be okay to delete it then?

    Plugin Author Hector Cabrera

    (@hcabrera)

    Yeah, that table is not in use anymore (I’m assuming here you’re using the latest version of the plugin of course) so you can delete it safely.

    Thread Starter oriver

    (@oriver)

    @hcabrera

    Thanks deleted it no problem, and your plugin still works perfectly, thank you.

    Plugin Author Hector Cabrera

    (@hcabrera)

    Hi @oriver,

    I’m sorry, I was wrong when I said that the popularpoststransients database table is not being used anymore. It is still being used by the plugin. I just completely forgot about it (as I said above), except I never really deleted it. I was thinking of a different table that did get removed from the plugin at some point, hence the confusion.

    If you’re not using the Data Caching feature on your website then you don’t need this table and you don’t need to do anything about it. However if you are using it then the table must be present for the Data Caching feature to work, see wp_popularpoststransients database error.

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

The topic ‘SQL Database’ is closed to new replies.