WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: Yet Another Related Posts Plugin] Browser freezing (19 posts)

  1. SkyWriting
    Member
    Posted 4 years ago #

    YAARP is always crashing/freezing my browser when I attempt to enter the options panel. The example display seems to be the problem. I don't need an answer. I'm just disabling the plugin on my sites. Too much overhead anyway.

  2. @SkyWriting - I've heard of such issues when a site has a large number of tags or categories. Is that the case for you?

    I've also heard in such cases that another browser such as Safari may be better than Firefox or IE.

  3. kosaytak
    Member
    Posted 4 years ago #

    I have the same problem. I have a large number of tags. The browser completely freezes and stop working.

  4. beggers
    Member
    Posted 4 years ago #

    I have the same problem. I have 2000+ posts and about 4000+ tags. The browser locks up as the tags start to load. There should be a way to disable the loading of all tags, especially if I'm not even using tags as a criteria.

    YARPP was really working great until I passed the 1000+ post mark. I love this program but it hangs up my browser every time I hit the options page.

    I haven't tried a cache program yet but I don't think it would solve this problem as long as the options page tries to load all my 4000+ tags.

    If you can resolve this I'd love to starting using YARPP again!

  5. Sorry, this issue has not been resolved yet. On the todo list.

  6. Antster
    Member
    Posted 4 years ago #

    Cheers Mitcho. Same problem here dude. Looking forward to using this plugin when resolved.

    Ant :-)

  7. ppskb
    Member
    Posted 4 years ago #

    Ditto,

    Great plugin, but hangs when there are lots of tags, or its a big post.

    Will have to disable until their is a fix.

    Cheers,
    Keith

  8. ppskb
    Member
    Posted 4 years ago #

    Or if you want to still use the plugin, you can change the "relatedness option" and select do not consider tags. This seems to speed up and prevent the page from crashing.

  9. @ppskb - not considering tags indeed does speed up things, but only the actual relatedness queries... this is totally unrelated to how the options screen hangs.

  10. rzeisler
    Member
    Posted 4 years ago #

    I was having similar browser freezing. I was using YARPP from day one with on issues. I was also using a small number of posts/tags/categories (less then 50 posts). I used a wordpress import/export file to import a large number of posts/tags/categories (2K posts/4.5K tags/50 categories) and at the same time upgraded from 3.1.6 to 3.1.7. I started experiencing long wait times when attempting to edit a post and always failing when trying to delete groups of posts (select a full page of posts to trash).

    I started looking a the linux server (Centos 5.4) using top and would see mysqld max out (100%) the cpu and not come back before the browser would timeout. I downgraded YARPP to the previous version (3.1.6) with no change in behavior. I then went through and deactivated all of my plugins. Now the same functions I tried (edit/delete) worked fine (as I expected). I then started reactivating my plugins one-by-one. Non problems with any of the plugins until I reactivated YARPP (3.1.6)...same mysqld pegging the cpu. I upgraded to 3.1.7 (just to verify that it wasn't a version issue) and it pegged the cpu as well. I then deactivated YARPP and mysqld behaved fine.

    I read this post and took the suggestion to turn off the "consider tags" option, activated YARPP (3.1.7) and all worked fine...cpu was not pegged by mysqld.

    One other note...this all started because of the slow response I noticed with wordpress. I attempted to tune the database by using the following params in my.cnf. The params are based on suggestions from mysqltuner.pl (a mysql tuner analysis script):

    # mysqltuner recommendations
    skip-innodb
    skip-bdb
    query_cache_size = 128M
    query_cache_limit = 16M
    tmp_table_size = 128M
    key_buffer_size = 128M
    max_heap_table_size = 32M
    thread_cache_size = 8
    table_cache = 512

    These params didn't appear to make a difference one way or another in the cpu maxing out when using YARPP with large number of tags.

    I was using 1GB of RAM and 1 CPU in a VMWare VServer 1.x environment when I started. I bumped up the RAM to 2GB and 2 CPUs with not difference in mysqld's behavior (except now I could suck up more then 100% of the CPUs).

    I hope this helps with tuning YARPP to handle large number of tags. It is an awesome add on and saves a lot of work with find related posts, something that I did in the old system by hand.

    One other item of info...I am using WordPress 2.9.2. This the version I have always used with YARPP. I just started using WordPress about a month ago and love it.

  11. @rzeisler thanks a lot for sharing your experience.

  12. Big Fish
    Member
    Posted 3 years ago #

    I have a large amount of tags and I'm experiencing the same problem.

  13. This is a known issue and I've been told some browsers handle this better than others. I hope to get around to implementing a workaround in the future.

  14. Big Fish
    Member
    Posted 3 years ago #

    Does 3.1.8 fix this issue?

  15. Big Fish, no, I did not tackle this in 3.1.8. :(

  16. Big Fish
    Member
    Posted 3 years ago #

  17. Big Fish,

    Well, yes, that would work, but ultimately I want to fix this so that the functionality is still available. Just made a ticket for it so I make sure to get to this:

    http://plugins.trac.wordpress.org/ticket/1144

  18. slfuller
    Member
    Posted 3 years ago #

    I wasn't crashing but GoDaddy (dare I admit I'm still hosting there) told me this was the plugin that was slowing down load times to something resembling dialup. 3.18 may have been contributing but it was actually another plugin that was causing the biggest problem. Things did seem to speed up a bit with today's 3.19.

  19. @slfuller glad to hear. I'm curious, though: what was that plugin? It's possible that YARPP and some other plugin interact in a negative way performance-wise, which is why I ask.

    Not all hosting is built alike, and it may indeed be, at the end of the day, that GoDaddy's database servers cannot handle YARPP's more database-intensive queries.

Topic Closed

This topic has been closed to new replies.

About this Topic