Skip to content

Performance

Problems with performance ?

19 Topics 284 Posts
  • 0 Votes
    1 Posts
    353 Views
    No one has replied
  • NodeBB socket with CloudFlare

    Unsolved
    23
    1 Votes
    23 Posts
    2k Views

    @DownPW it’s your only realistic option at this stage.

  • error with v3 in browser console

    Solved
    4
    0 Votes
    4 Posts
    168 Views

    @DownPW it’s in relation to the response I provided above

  • 3 Votes
    4 Posts
    152 Views

    @Panda You should be able to use {% javscript %} as shown in this video - it’s quite the watch, but very educational, and provides insight as to how this works - see below screenshot for an example

    cdb160e9-d955-498c-b921-982db2986e2b-image.png

  • NodeBB v3 Chat Very Slow

    Moved
    47
    11 Votes
    47 Posts
    3k Views

    @DownPW Seems fine.

  • SEO and Nodebb

    2
    2 Votes
    2 Posts
    150 Views

    @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.

  • 0 Votes
    2 Posts
    156 Views

    @eeeee they are nothing to worry about, and can be ignored.

  • NodeBB v3.0.0-rc.1

    1
    1 Votes
    1 Posts
    90 Views
    No one has replied
  • 3 Votes
    4 Posts
    621 Views

    @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.

  • 14 Votes
    69 Posts
    5k Views

    @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/

  • Virtualmin SQL problem

    Solved
    39
    3 Votes
    39 Posts
    1k Views

    @DownPW said in Virtualmin SQL problem:

    Finally problem solved simply but I still don’t understand why this service was installed.

    Glad to hear (and see) that this issue is now resolved. Virtualmin and Webmin are both derived from the origin of LAMP (Linux, Apache, MySQL, and PHP) - the earliest form would have been a project which was a fork of the original concept called “WAMP” (Windows, Apache, MySQL, and PHP)

    https://www.wampserver.com/en/

    Scroll to the bottom, and you’ll see the packages it comes with

    cf3c0965-a699-4c6f-b89f-65e7bb381bbc-image.png

    Over time, activity on this project dropped somewhat due to the rise of Virtualmin and Webmin - acting as “full blown” platforms designed to manage an entire web server from start to finish, and providing an easy way to do so with a GUI interface. Over time, the LAMP bundle became LEMP (Linux, NGINX [actually pronounced “engine X”], MySQL, and PHP). The issue with Apache is that it had limits, and compared to NGINX, was in fact much slower.

    Virtualmin and Webmin do not actually use MySQL for their core operation - they don’t even use Apache or NGINX for the core web services, which is why the admin port is set to a default of 10000 when you first complete the setup.

    Essentially, you can think of Virtualmin and Webmin as a central pane of glass to manage the underlying components that are required to run a website. MySQL doesn’t need to be installed if you are not actually using it, but is there as PHP typically is paired with either MySQL or MariaDB, so it makes sense to offer the installation of this itself, as well as support for managing it.

  • 1 Votes
    3 Posts
    242 Views

    @qwinter yes, I recently migrated this site to CF in full and noticed the same thing. Seems CF also has native socket support now under the free plan, so win/win. I’ve not noticed any degradation of service since moving so happy to stay put for the time being.

  • Nord VPN & Bitdefender

    Solved
    8
    1 Votes
    8 Posts
    382 Views

    @JAC been working fine. No complaints from me

  • nodeJS is the best

    Solved
    9
    5 Votes
    9 Posts
    567 Views

    no no no

    @DownPW said in nodeJS is the best:

    hmmm I’ve already had this on my forum !!!

  • Do i need more RAM? Plesk

    Solved
    3
    1 Votes
    3 Posts
    260 Views

    @Hari welcome to Grafana, the most confusing stats package there is !

    According to the guidelines, you certainly have enough RAM at 4gb

    https://www.plesk.com/blog/various/plesk-requirements-hardware-software/

  • NodeBB slow after DB recovery

    Solved
    1
    5 Votes
    1 Posts
    250 Views
    No one has replied
  • NodeBB 1.19.3

    Solved
    33
    4 Votes
    33 Posts
    3k Views

    @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

    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

  • unable to upvote on forum

    Solved
    10
    3 Votes
    10 Posts
    553 Views

    @phenomlab yes, i can understand. it is working now 🙂

  • 11 Votes
    21 Posts
    1k Views

    @jac @Hari my thoughts around this are that with any platform - be that WordPress, Flarum, or NodeBB, there is an inevitable “lock in” - very much like Hotel California (“you can check out any time you like, but you can never leave”).

    What I mean by this is that you are buying into an ecosystem that offers no easy or readily available path out. If you plan to stay for the long term and there is a clear progression path from that project meaning it’s a viable route, then great.

    However, all of these platforms (except WordPress perhaps) have a way of ingesting data from other sources, but little to no way at all of taking that data somewhere else. This is nothing against any of those platforms, but the fundamental issue here is that whilst it’s probably easy to move into another product, it’s a different story altogether when you want to leave and take your data with you.

    Most FOSS based platforms can realise this and make money out of migrations. I know for certain that wpForo does this, and I also know that it’s something that one of the developers at Flarum has been touting for some time.