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.
  • Bug Report

    Solved Bugs nodebb bugs
    47
    1
    26 Votes
    47 Posts
    20k Views
    phenomlab
    @crazycells Good points, thanks. I completely forgot that classes are added - makes life much simpler! EDIT - seems this is pretty straightforward, and only needs the below CSS .upvoted i { color: var(--bs-user-level) !important; } This then yields [image: 3f072f8a-ebfa-4910-8723-73c493b8e4eb-image.png] However, the caveat here is that the .upvoted class will only show for your upvotes, and nobody else’s. However, this does satisfy the original request however I would love to see my upvoted posts more clearly, because currently, when I upvote, nothing on the post tool is changing, it would be nicer if there is an indication that I have upvoted (like a filled or colored triangle?)
  • Nodebb 3.2.0

    Bugs nodebb nodebb 3.2.0
    20
    1
    2 Votes
    20 Posts
    7k Views
    phenomlab
    @crazycells yes, I’m aware of that. Need to fix EDIT- fixed. Caused by the same CSS that is used to absolutely position the “verified” group badge in the posts view. Amended this CSS so that is specifically targets the post stream as below li[component="post"] a[href*="/groups/verified"] { position: absolute !important; left: 8px; z-index: 2; margin-top: 1px; border-radius: 999px !important; line-height: 14px; display: block; height: 22px; margin-left: 0px !important; }
  • 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.
  • 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: The global Search option

    Solved Configure search nodebb
    5
    0 Votes
    5 Posts
    1k Views
    phenomlab
    @mventures Yes, exactly. The other icon will restart NodeBB whilst the first icon I referenced will rebuild (recompile) it. The huge strength of NodeBB over Flarum (for example) is that the code is precompiled, and called once at boot. PHP’s code has to repeatedly reload code from source making it much slower.
  • [NodeBB] greeting message

    Solved Customisation css nodebb javascript
    2
    1
    3 Votes
    2 Posts
    2k Views
    phenomlab
    @pwsincd welcome to sudonix, and thanks for the comments. What your looking for is here https://sudonix.com/topic/195/nodebb-welcome-message/3?_=1648295651358