Skip to content

NodeBB v3 Chat Very Slow

Moved Performance
47 3 20.9k 1
  • wrote on last edited by
    #1

    Hi Mark
    Chat area is very slow after uprading. Keyboard is very slow and it is locked some times.

  • Hi Mark
    Chat area is very slow after uprading. Keyboard is very slow and it is locked some times.

    wrote on last edited by
    #2

    @cagatay I’m testing this on your site from my PC - responses are immediate with no delays. have you tried clearing the cache on your browser, and the Cloudflare cache ? I am unable to replicate this issue - could you try with another web browser and see if the issue persists ?

  • wrote on last edited by
    #3

    it was via android phone not computer. maybe it was a problem?

  • it was via android phone not computer. maybe it was a problem?

    wrote on last edited by
    #4

    @cagatay I’m also testing from my Android phone and unable to replicate.

  • wrote on last edited by
    #5

    @cagatay I’m not convinced that this is coming from your server, or NodeBB. Having tested myself, it works instantly for me.

  • phenomlab phenomlab moved this topic from Bugs on
  • wrote on last edited by
    #6

    it’s odd, It’s not all the time but I had the same problem on Sudonix on Smartphone yesterday or before last night.
    I would have to look at my instance

  • it’s odd, It’s not all the time but I had the same problem on Sudonix on Smartphone yesterday or before last night.
    I would have to look at my instance

    wrote on last edited by
    #7

    @DownPW interesting. You both use Android from memory as I do, but I’ve yet to come across this.

  • wrote on last edited by
    #8

    This is certainly interesting. Looks like others are reporting the same issue

    https://community.nodebb.org/topic/17167/reduce-speed-in-v3-0-0/8?_=1683170989623

  • wrote on last edited by
    #9

    Chat page is freezing, speed is ok but sometimes it is freezing.

  • Chat page is freezing, speed is ok but sometimes it is freezing.

    wrote on last edited by
    #10

    @cagatay This is going to be something that NodeBB themselves need to address.

  • @cagatay This is going to be something that NodeBB themselves need to address.

    wrote on last edited by
    #11

    @phenomlab yes i think so.

  • wrote on last edited by
    #12

    this is one of the reasons why I haven’t upgraded to V3 yet.
    I’m waiting for a fix from nodeBB for this bug.

    A topic has been created on nodebb forum communauty but does not provide an answer.

  • this is one of the reasons why I haven’t upgraded to V3 yet.
    I’m waiting for a fix from nodeBB for this bug.

    A topic has been created on nodebb forum communauty but does not provide an answer.

    wrote on last edited by
    #13

    @DownPW I think @julian is aware of this issue as he has responded to the NodeBB thread However, I’d agree that response isn’t as fast as some would expect.

  • wrote on last edited by
    #14

    @DownPW @cagatay have either of you tried clearing your browser and CF caches completely to see if this resolves the issue? I have experienced this once on this forum since upgrading, cleared all caches, and the problem hasn’t returned since (for me at least)

  • wrote on last edited by
    #15
  • wrote on last edited by
    #16

    yes we tested with baris, will be fixed 3.1.4

  • yes we tested with baris, will be fixed 3.1.4

    wrote on last edited by
    #17

    @cagatay 3.1.4 has been released.

    c37e8803-9538-44bc-9158-7073cffb5cb3-image.png

  • @cagatay 3.1.4 has been released.

    c37e8803-9538-44bc-9158-7073cffb5cb3-image.png

    wrote on last edited by
    #18

    @phenomlab upgraded thank you 🙂

  • wrote on last edited by
    #19

    I need to upgrade and do my CSS themes but I have no time grrr

    I work on the garden 🙂

  • I need to upgrade and do my CSS themes but I have no time grrr

    I work on the garden 🙂

    wrote on last edited by
    #20

    @DownPW said in NodeBB v3 Chat Very Slow:

    I work on the garden

    Ha ha 🤣 no rest for you then!


Related Topics
  • NodeBB socket with CloudFlare

    Solved Performance socket cloudflare nodebb
    24
    3 Votes
    24 Posts
    14k Views
    DownPW
    Solved. Tuto here and here
  • error with v3 in browser console

    Solved Performance socket error csrf
    4
    1
    0 Votes
    4 Posts
    2k Views
    phenomlab
    @DownPW it’s in relation to the response I provided above
  • SEO and Nodebb

    Performance nodebb seo
    2
    2 Votes
    2 Posts
    2k Views
    phenomlab
    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1 However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365 And also https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164 It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”. Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.
  • NODEBB: Nginx error performance & High CPU

    Solved Performance performance nodebb nginx
    69
    4
    14 Votes
    69 Posts
    63k Views
    DownPW
    @phenomlab Seems to be better with some scaling fix for redis on redis.conf. I haven’t seen the message yet since the changes I made # I increase it to the value of /proc/sys/net/core/somaxconn tcp-backlog 4096 # I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! #save 900 1 #save 300 10 #save 60 10000 If you have other Redis optimizations. I take all your advice https://severalnines.com/blog/performance-tuning-redis/
  • NodeBB v3

    Announcements nodebb v3 nodebb
    2
    3 Votes
    2 Posts
    1k Views
    phenomlab
    @cagatay JS will work fine - no changes there, and there are no plans to drop support for jQuery. More of an issue is the CSS - for which there are quite a few breaking changes. Keep an eye on sudonix.dev (my development site) where you can see progress in relation to how I am tackling the compatibility issues.
  • NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    33
    4 Votes
    33 Posts
    16k Views
    DownPW
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok
  • [NodeBB] Import custom Font

    Solved Customisation custom fonts nodebb css
    12
    3 Votes
    12 Posts
    5k Views
    phenomlab
    @cagatay you’ll need to define this in the body tag (or another element if you want greater or more granular targets) - for example body { font-family: "Poppins"; font-size: 16px; } Essentially, you use the font-size CSS directive.
  • NodeBB Design help

    Solved Customisation
    8
    3
    2 Votes
    8 Posts
    4k Views
    phenomlab
    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ? For the record, this is what I added #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; } The /categories page seems a bit messed up, so looking at that currently EDIT - issued some override CSS in the CATEGORIES widget <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style> That should resolve the /categories issue.