Skip to content
Sudonix

sudonix

NodeBB v3 Chat Very Slow

Moved Performance
Log in to reply

20/47

19 May 2023, 18:56

Related Topics
  • Pandaundefined

    Test of youtube embeds

    Solved Configure
    47 20 Aug 2024, 08:41
    20 Aug 2024, 08:41
    11 Votes
    14 Posts
    323 Views
    Sampo2910undefined
    @phenomlab Perfect!!! Many thanks.
  • DownPWundefined

    error with v3 in browser console

    Solved Performance
    47 26 Jul 2023, 08:42
    26 Jul 2023, 08:42
    1
    0 Votes
    4 Posts
    284 Views
    phenomlabundefined
    @DownPW it’s in relation to the response I provided above
  • Pandaundefined

    Nodebb design

    Solved General
    47 11 Jul 2023, 10:13
    11 Jul 2023, 10:13
    1 Votes
    2 Posts
    320 Views
    phenomlabundefined
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Pandaundefined

    SEO and Nodebb

    Performance
    47 4 Jul 2023, 09:11
    4 Jul 2023, 09:11
    2 Votes
    2 Posts
    345 Views
    phenomlabundefined
    @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.
  • Pandaundefined

    build nodebb Warning in entrypoint size limit

    Solved Performance
    47 15 Apr 2023, 20:03
    15 Apr 2023, 20:03
    0 Votes
    2 Posts
    253 Views
    phenomlabundefined
    @eeeee they are nothing to worry about, and can be ignored.
  • DownPWundefined

    NODEBB: Nginx error performance & High CPU

    Solved Performance
    47 17 Dec 2022, 21:42
    17 Dec 2022, 21:42
    4
    14 Votes
    69 Posts
    14k Views
    DownPWundefined
    @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/
  • phenomlabundefined

    NodeBB slow after DB recovery

    Solved Performance
    47 28 Feb 2022, 17:42
    28 Feb 2022, 17:42
    5 Votes
    1 Posts
    307 Views
    No one has replied
  • RiekMediaundefined

    NodeBB Design help

    Solved Customisation
    47 16 Oct 2021, 12:56
    16 Oct 2021, 12:56
    3
    2 Votes
    8 Posts
    1k Views
    phenomlabundefined
    @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.