Database queries caused Bluehost deactivation - "related" plug-ins the issue? (11 posts)

  1. mvanpatten
    Posted 4 years ago #

    GoingLikeSixty.com was deactivated Saturday. I was told that the taxonomy was causing too many database queries. I was guided to look in tmp/slow_database_queries where there is a log file.

    Bluehost tech support said that plug-ins that add related posts can cause this issue.

    I deactivated them all. Then added them back one at a time. All seemed well until I looked at log files this morning and the issue is back.

    Bluehost.com said they had throttled the site 6000 seconds the past hour.

    So I deactivated plug-ins again:
    Contextual Related Posts
    Version 1.6.3

    Version 0.85

    nRelate Related Content
    Version 0.46.0

    upPrev Previous Post Animated Notification
    Version 1.4.0

    These had all been humming right along until 3.1.2 upgrade.

    Perhaps I need to wait longer between reactivating each plug-in to isolate the problem?

    Am I on the right track?

    Anybody having similar problems? Suggestions?

  2. BlazeForce
    Posted 4 years ago #

    What are you using for a caching plugin?

  3. mvanpatten
    Posted 4 years ago #

    WP Super Cache.

    I have now disabled everything: plug-ins, ads, stats and Bluehost says this last hour the throttling has been removed. The past hour I was throttled 22 minutes out of sixty.

  4. BlazeForce
    Posted 4 years ago #

    This has happened to me before. Try using the DB Cache Reloaded instead of Super Cache and see if that handles better.

  5. mvanpatten
    Posted 4 years ago #

    Will do.

  6. Chip Bennett
    Theme Review Admin
    Posted 4 years ago #

    I highly recommend W3 Total Cache.

    Also, Efficient Related Posts does a very nice job of querying related posts efficiently, and caching the query results. So, IMX it uses less resources.

  7. mvanpatten
    Posted 4 years ago #

    The throttling has stopped. Unknown why. However a new problem popped up today that I think is related. I needed to "reset" my permalinks to make the commenting work.

    I am now trying W3 Total Cache.

  8. mvanpatten
    Posted 4 years ago #

    Yeah, the caching is the issue. When I deployed W3 Total Cache the comments were borked: white page.

    So screw caching, don't need it anyway for teeny-weeny blog. I just want a site that is up...thot caching plug-in would be right thing to do.

    And BTW: Pingdom is worthless. I haven't been notified of downtime and the site has been throttled for three days.

  9. bh_WP_fan
    Posted 4 years ago #

    Downtime and slowness aren't the same thing. A service can't notify you of downtime if your site is working but is slow.

    If W3TC isn't working for you, it may be your configuration, or it may be clashing with another plugin. Regardless of how small your site may be, caching is a good thing to do and, if you are getting throttled a lot, regardless of how small you may think it is... it isn't. If you don't want to try W3TC, try WP Super Cache.

  10. mvanpatten
    Posted 4 years ago #

    @bh_WP_fan: thanks for your guidance. I had been using WP Super Cache for years until this. I switched to W3TC based on Chip Bennett's suggestion then deactivated when throttling continued.

    I will try DB Cache Reloaded that Blaze recommended.

  11. bh_WP_fan
    Posted 4 years ago #

    I don't know how far your optimization has gone, but there are several really good tips here that should help you as well. Look into these for some CPU/Throttling tips.

Topic Closed

This topic has been closed to new replies.

About this Topic