• Has anyone had an issue with their host disabling they DB because of this:

    It has come to our attention that your hosting account, specifically the **** database is causing the shared resources to be over-utilized. This, in turn, affects the usage by other customers.

    We have disabled your database to return the server to normal usage. To re-enable your database, you will need to correct the following query:

    I read it was suggested YARPP be used with Super Cache however I have been using Hyper Cache plugin. Does this make a difference?

    https://www.ads-software.com/extend/plugins/yet-another-related-posts-plugin/

Viewing 4 replies - 1 through 4 (of 4 total)
  • this should solve the problem:

    https://www.ads-software.com/extend/plugins/wp-super-cache/

    your sites become static pages which do not require a new sql query everytime a surfer visits the site.

    @MannyStudios, I’m not familiar with HyperCache but, as @geeman12030 suggested, I do recommend the use of WP Super Cache with YARPP. You may also consider turning off considering tags, considering categories, or “cross-relate posts and pages” as each of these options makes YARPP’s database queries heavier. Best of luck.

    Any experience with w3 total cache? I am also curious on how we cab minimize the footprint of yarpp when saving new posts, it seems to be very db intensive. which options should we use to minimize the number of db queries when saving in admin and still get interesting results?

    I don’t have any experience with w3 total cache myself, so I’m not sure.

    From the FAQ:
    If you find that the YARPP database calls are still too database-intensive, try turning off “cross relate posts and pages,” not considering tags and/or categories in the Relatedness formula, and not excluding any tags and/or categories in The Pool. All of these will improve database performance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: Yet Another Related Posts Plugin] YARPP caused host to disable my DB’ is closed to new replies.