Skip to content

NodeBB v3 Chat Very Slow

Moved Performance
47 3 21.3k 1
  • Odd, node like that on nodebb communauty

    wrote on last edited by
    #31

    @DownPW as I said previously, likely a regression introduced by 3.2.0

  • wrote on last edited by
    #32

    But nodebb forum communauty is on 3.2.0 no ?
    If yes, they don’t have this problem

  • wrote on last edited by
    #33

    They deactivate background and box shadow on nodebb communauty :

    image.png

  • They deactivate background and box shadow on nodebb communauty :

    image.png

    wrote on last edited by
    #34

    @DownPW None of those will impact the box size. Let me have a look.

  • wrote on last edited by
    #35

    yep not box size but we don’t see the bug

  • yep not box size but we don’t see the bug

    wrote on last edited by
    #36

    @DownPW what exactly is the bug? I’ve tested it, and it behaves normally from what I see (unless I completely missed something)?

  • wrote on last edited by
    #37

    Size is good, is just the focus when we type text it has changed

    on 3.1.7 :

    image.png

    On 3.2.0 here :

    6e7b686d-031c-4e98-927e-a5df67906c25-image.png

  • Size is good, is just the focus when we type text it has changed

    on 3.1.7 :

    image.png

    On 3.2.0 here :

    6e7b686d-031c-4e98-927e-a5df67906c25-image.png

    wrote on last edited by
    #38

    @DownPW Yes, that’s input:focus - it’s used to style much larger boxes on focus, but I’ll need to create an exemption here.

  • wrote on last edited by
    #39

    Nodebb communauty :

    image.png

  • Nodebb communauty :

    image.png

    wrote on last edited by phenomlab
    #40

    @DownPW @cagatay Thanks for reporting. Should match now.

    f99597be-2d44-4c14-a46d-c803de6d9347-image.png

  • wrote on last edited by
    #41

    yep better 🙂

    Solution ?

  • yep better 🙂

    Solution ?

    wrote on last edited by phenomlab
    #42

    @DownPW As you indicated, but I need to make this more specific because it disables a wanted UI experience elsewhere

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        /*box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important; */
        border-color: transparent !important;
    }
    

    Starting with this CSS

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        border-color: transparent !important;
    }
    .write-container .form-control:focus {
        box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important;
    }
    
  • wrote on last edited by
    #43

    Have you find better solution or this is the final @phenomlab ?

  • Have you find better solution or this is the final @phenomlab ?

    wrote on last edited by
    #44

    @DownPW this is the final solution from my perspective. The above code resolves the issue here.

  • Have you find better solution or this is the final @phenomlab ?

    wrote on last edited by
    #45

    @DownPW i m also using last codes on my web site.

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        border-color: transparent !important;
    }
    .write-container .form-control:focus {
        box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important;
    }
    
  • wrote on last edited by
    #46

    I have search and I use this code. What do you think ?

    textarea.bg-transparent.text-body.form-control.chat-input.mousetrap.rounded-0.border-0.shadow-none.ps-1.py-0 {
        box-shadow: 0 0 0 1px transparent inset !important;
    }
    
  • I have search and I use this code. What do you think ?

    textarea.bg-transparent.text-body.form-control.chat-input.mousetrap.rounded-0.border-0.shadow-none.ps-1.py-0 {
        box-shadow: 0 0 0 1px transparent inset !important;
    }
    
    wrote on last edited by
    #47

    @DownPW Seems fine.


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
    6k 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.
  • NodeBB socket with CloudFlare

    Solved Performance socket cloudflare nodebb
    24
    3 Votes
    24 Posts
    14k Views
    DownPW
    Solved. Tuto here and here
  • 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.
  • Optimum config for NodeBB under NGINX

    Performance nginx performance
    4
    3 Votes
    4 Posts
    3k Views
    phenomlab
    @crazycells hi - no security reason, or anything specific in this case. However, the nginx.conf I posted was from my Dev environment which uses this port as a way of not interfering with production. And yes, I use clustering on this site with three instances.
  • Setting up a beta NodeBB v3 environment

    Moved Let's Build It nodebb upgrades beta1
    14
    3
    11 Votes
    14 Posts
    6k Views
    phenomlab
    @dave1904 excellent news. Thanks for the feedback
  • NODEBB: Nginx error performance & High CPU

    Solved Performance performance nodebb nginx
    69
    4
    14 Votes
    69 Posts
    64k 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
    972 Views
    No one has replied