• Resolved jamminjames

    (@jamminjames)


    We’ve been experiencing some problems with spikes on our dedicated server causing the website to basically shut down.

    Our tech put a monitor on it, and says that spikes they saw coincide with occasions of an UPDATE query responsible for about 75% of the database writes in the log over a one day period. He gave this info:

    The query minus all the data is as follows:
    442878 Query UPDATE wp_options SET option_value WHERE option_name = ‘top_opt_already_tweeted_posts’

    A portion of the data is as follows:
    i:0;s:5:\”32729\”;i:1;s:5:\”32898\”;i:2;s:5:\”32726\”;i:3;s:5:\”32832\”;

    Does Revive Old Post need to write to the database so much? Is it a function of settings? Does it have anything to do with Excluded Posts settings? If so, can those be disabled? (I don’t see any way of deleting the Exclude setting for past posts.)

    https://www.ads-software.com/plugins/tweet-old-post/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor selu

    (@marius2012)

    Mmm, that’s strange, ROP update that option only when the cron is triggered, i.e when the posts are send to the social networks. Can you share with us the file from Revive Old Post -> System info at [email protected] to replicate the issue on my end.

    Thank you !

    Thread Starter jamminjames

    (@jamminjames)

    I emailed that yesterday.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Turn off excessive writing to database?’ is closed to new replies.