Viewing 15 replies - 31 through 45 (of 51 total)
  • @davidgustav – it’s possible that the settings you’re using is just too computationally intensive for your server. There are some tips for this in the FAQ.

    @mitchoyoshitaka Thanks, I’ll take a look. It had been running fine for 6 months with no settings changed. The upgrade to 2.9 is the only variable I can think of right now. Unless the number of posts grew too fast I guess…

    @davidgustav – hopefully the caching will take care of it and keep it under control after a while too. Best of luck.

    I don’t know… the plugin has been sitting there, with the same options, for many months now…
    only after upgrading to WP2.9 – and to YARPP 3.1.1 – on the same day (I know, I shouldn’t have upgraded on the same day… but releases of EVERYTHING and anything are way too frequent these days… but I digress…:-)) I noticed the high load.
    look at this pic https://www.muscetta.com/images/WP29YARPP311load.png
    in that picture you can see the load until last sunday… the CPU getting a lot busier after the upgrade on sunday… being busy a couple of days…
    halfway tuesday the load decreases (I changed settings saying not to consider tags and categories anymore) but still being busy… then, ultimately, on saturday, the load getting back to its previous level after I deactivated the plugin.
    I am now giving the beta a try.

    I have tried beta release also..but it still causes high load…

    FYI, in MY testing (3 hours…) the latest beta seems to be slightly less heavy.

    Anyhow, I think I found the culprit: the highEST load on my server was caused by the calculation of related posts when pulling the RSS feed… which was causing the recalculation of related posts for ALL posts in the feed (50 posts, in my case!).
    Disabling the feature from feeds it seems to go A LOT better… but I am not quote sure as WHY I had not seen this before, in previous versions – I don’t remember changing any option…

    @dani3l3 – the RSS forces all those posts’ related posts to be calculated at once, for a single request (though it’s cached afterwards) so it is indeed intensive, particuarly at the beginning. If turning it off works for you, though, I’m glad. ?? Feel free to turn it back on after a while of caching… this action should not reset the cache so you shouldn’t notice any spike then.

    @hifa, perhaps that would help for you as well.

    ok, I confirm that with the latest beta and with the option of the RSS disabled the CPU has been a lot quiter (more or less at the level it was earlier) for the last 12 hours.
    I just don’t remember having ENABLED the option now – I don’t actually remember having changed any option at all during of just after upgrading…
    might it be some change in core related to RSS the way feeds are handled, if the plugin’s code did not change?

    @dani3l3 that is possible, and unfortunately I don’t know about those changes. :/

    Major issues… Absolutely major.

    After 3-4 days of problems with the database. My webhost finally shut us down with the following email:

    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:

    INSERT INTO fgt_yarpp_related_cache (reference_ID,ID,score)
    (SELECT 842, ID, (0+ (MATCH (post_content) AGAINST (‘enjoy share ‘)) *
    1+ (MATCH (post_title) AGAINST (‘stones chimaera ‘)) * 1+ COUNT(
    DISTINCT tagtax.term_taxonomy_id ) * 1+ COUNT( DISTINCT
    cattax.term_taxonomy_id ) * 1) as score from fgt_posts
    LEFT join fgt_term_relationships as blockrel on (fgt_posts.ID = blockrel.object_id)
    LEFT join fgt_term_taxonomy as blocktax using (term_taxonomy_id)
    LEFT join fgt_terms as blockterm on (blocktax.term_id = blockterm.term_id and blockterm.term_id in (1))
    LEFT JOIN fgt_term_relationships AS thistag ON (thistag.object_id = 842 )
    LEFT JOIN fgt_term_relationships AS tagrel on (tagrel.term_taxonomy_id = thistag.term_taxonomy_id
    AND tagrel.object_id = fgt_posts.ID)
    LEFT JOIN fgt_term_taxonomy AS tagtax ON ( tagrel.term_taxonomy_id = tagtax.term_taxonomy_id
    AND tagtax.taxonomy = ‘post_tag’)
    LEFT JOIN fgt_term_relationships AS thiscat ON (thiscat.object_id = 842 )
    LEFT JOIN fgt_term_relationships AS catrel on (catrel.term_taxonomy_id = thiscat.term_taxonomy_id
    AND catrel.object_id = fgt_posts.ID)
    LEFT JOIN fgt_term_taxonomy AS cattax ON ( catrel.term_taxonomy_id = cattax.term_taxonomy_id
    AND cattax.taxonomy = ‘category’)
    WHERE (post_status IN ( ‘publish’, ‘static’ ) and ID != ‘842’) and post_password =”
    GROUP BY id
    HAVING score >= 1.00 and count(blockterm.term_id) = 0 order by score
    desc limit 5) union (SELECT 842, ID, (0+ (MATCH (post_content) AGAINST
    (‘enjoy share ‘)) * 1+ (MATCH (post_title) AGAINST (‘stones chimaera
    ‘)) * 1+ COUNT( DISTINCT tagtax.term_taxonomy_id ) * 1+ COUNT( DISTINCT
    cattax.term_taxonomy_id ) * 1) AS score FROM fgt_posts
    LEFT join fgt_term_relationships as blockrel on (fgt_posts.ID = blockrel.object_id)
    LEFT join fgt_term_taxonomy as blocktax using (term_taxonomy_id)
    LEFT join fgt_terms as blockterm on (blocktax.term_id = blockterm.term_id and blockterm.term_id in (1))
    LEFT JOIN fgt_term_relationships AS thistag ON (thistag.object_id = 842 )
    LEFT JOIN fgt_term_relationships AS tagrel on (tagrel.term_taxonomy_id = thistag.term_taxonomy_id
    AND tagrel.object_id = fgt_posts.ID)
    LEFT JOIN fgt_term_taxonomy AS tagtax ON ( tagrel.term_taxonomy_id = tagtax.term_taxonomy_id
    AND tagtax.taxonomy = ‘post_tag’)
    LEFT JOIN fgt_term_relationships AS thiscat ON (thiscat.object_id = 842 )
    LEFT JOIN fgt_term_relationships AS catrel on (catrel.term_taxonomy_id = thiscat.term_taxonomy_id
    AND catrel.object_id = fgt_posts.ID)
    LEFT JOIN fgt_term_taxonomy AS cattax ON ( catrel.term_taxonomy_id = cattax.term_taxonomy_id
    AND cattax.taxonomy = ‘category’)
    WHERE (post_status IN ( ‘publish’, ‘static’ ) and ID != ‘842’) and post_password =”
    GROUP BY id
    HAVING score >= 1.00 and count(blockterm.term_id) = 0 order by score desc limit 5) on duplicate key update date = now()

    Disabling the YARPP plugin will resolve this issue.

    @sjgold At a quick glance I can’t see anything wrong with that query… if it’s simply that it’s too computationally intensive, turning off any disallowed tags or categories, and not considering tags and categories would both help performance.

    I assume you’re using the latest version?

    @sjgold thanks for reporting that..I was seeking solution for since 2.9 upgrade..
    and @mitchoyoshitaka taken ur recommendation and I unchecked tags, categories from relatedness..
    voila..no excessive load, no high cpu any more..

    using yarpp after a long time again..

    Thanks!

    @hifa great!

    First, thanks for a great plugin, I really like it and am amazed to see how responsive you are!

    In upgrading to WP 2.9 and then today 2.9.1, I noticed that some of my dashboard functionality disappeared (can’t view recent comments or WP news for instance) and had lost the ability to edit some pages but not all. Very strange! I figured it was YARRP by deactivating and reactivating all the plug ins, and the problem is mostly fixed by upgrading to YARPP 3.1.3 but I have still lost a few items on the dashboard (recent comments, WP news.) I’d rather have YARPP activated than these features, but am worried about the feed problems some others have mentioned. I’m at https://danigirl.ca/blog. Thougths?

    Just to follow up on Danigirl’s observations:

    After upgrading a couple blogs to 2.9.1 I’ve noticed similar problems with the Dashboard while using YARPP 3.1.3 (even as the only activated plug-in). The left nav and Right Now callout will be the only panels showing – the rest of the page being blank.

    Also, the ability to upload images via Media or Add an Image was simultaneiously affected. After selection and submission of a moderately sized file, the process fail to make it to the next step.

    Deactivating YARPP 3.1.3 returns functionality to normal.

Viewing 15 replies - 31 through 45 (of 51 total)
  • The topic ‘[Plugin: Yet Another Related Posts Plugin] Broken in 2.9?’ is closed to new replies.