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
  • 4 Votes
    3 Posts
    2k Views
    crazycells
    thanks @DownPW ! this is definitely very helpful.
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    5k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • Opening links in nodebb widget

    Solved Configure nodebb
    6
    4 Votes
    6 Posts
    3k Views
    phenomlab
    A more efficient way of including this would be to not over complicate it and leverage a standard iframe (providing the CSP headers of the remote site permit this) like below <iframe src="https://www.classmarker.com/online-test/start/?quiz=gag66aea7922f0a5" width="700" height="800"></iframe> This works first time every time on your site as intended.
  • build nodebb Warning in entrypoint size limit

    Solved Performance nodebb
    2
    0 Votes
    2 Posts
    1k Views
    phenomlab
    @eeeee they are nothing to worry about, and can be ignored.
  • 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 slow after DB recovery

    Solved Performance performance nodebb
    1
    5 Votes
    1 Posts
    967 Views
    No one has replied
  • NodeBB Footer

    Solved Customisation footer nodebb
    10
    1 Votes
    10 Posts
    4k Views
    JAC
    @phenomlab said in NodeBB Footer: @jac and you. Hope all is well and you recover quickly Thanks pal
  • NodeBB metadata

    Solved Configure nodebb
    4
    2 Votes
    4 Posts
    2k Views
    JAC
    @phenomlab said in NodeBB metadata: @jac Are you sure ? https://www.google.co.uk/search?q=site%3Astockportcounty.fans&sxsrf=AOaemvLwnaZL-PliU_2dBOg_Eo1pMVhBjg%3A1638982328139&source=hp&ei=uOKwYeatBcOsad3yp7AE&iflsig=ALs-wAMAAAAAYbDwyLBSDcG5XYoFCKwQFhgz94wTxOcV&ved=0ahUKEwjm6dX71NT0AhVDVhoKHV35CUYQ4dUDCAk&uact=5&oq=site%3Astockportcounty.fans&gs_lcp=Cgdnd3Mtd2l6EAM6BAgjECc6CwgAEIAEELEDEIMBOg4ILhCABBCxAxDHARCjAjoRCC4QgAQQsQMQgwEQxwEQowI6BQguEIAEOggIABCABBCxAzoFCAAQgAQ6CAguELEDEIMBOgsILhCABBDHARCvAToICC4QgAQQsQM6BQgAELEDOgsILhCABBDHARDRAzoLCAAQgAQQsQMQyQM6BQgAEJIDUABYySZg0CdoAHAAeACAAW2IAa0NkgEEMjMuMpgBAKABAQ&sclient=gws-wiz Fair enough 🤪🤪.