Sudonix

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

NodeBB v3.0.0-rc.1

Performance

1 Posts 1 Posters 40 Views

undefined Offline

undefined Offline
cagatay
wrote on last edited by

#1

Released, who is using and pls share with us your experincess
1 Reply Last reply
1
undefined cagatay marked this topic as a regular topic on

undefined

NodeBB socket with CloudFlare
Scheduled Pinned Locked Moved Unsolved Performance socket cloudflare nodebb
23

1 Votes

23 Posts

430 Views

undefined

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

SEO and Nodebb
Scheduled Pinned Locked Moved Performance nodebb seo
2

2 Votes

2 Posts

43 Views

undefined

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

NodeBB v3 Chat Very Slow
Scheduled Pinned Locked Moved Performance nodebb v3 nodebb chat
47

11 Votes

47 Posts

523 Views

undefined

@DownPW Seems fine.
undefined

build nodebb Warning in entrypoint size limit
Scheduled Pinned Locked Moved Solved Performance nodebb
2

0 Votes

2 Posts

61 Views

undefined

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

Optimum config for NodeBB under NGINX
Scheduled Pinned Locked Moved Performance nginx performance
4

3 Votes

4 Posts

467 Views

undefined

@crazycells hi - no security reason, or anything specific in this case. However, the nfinx.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.
undefined

NODEBB: Nginx error performance & High CPU
Scheduled Pinned Locked Moved Solved Performance performance nodebb nginx
69

14 Votes

69 Posts

978 Views

undefined

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

NodeBB slow after DB recovery
Scheduled Pinned Locked Moved Solved Performance performance nodebb
1

5 Votes

1 Posts

184 Views

undefined

One thing I noticed was that after recovering the assets and database onto a test server: (see below)

https://sudonix.com/topic/239/testing-out-webdock-io

The performance of the replica NodeBB install was painfully slow. After much searching and hair pulling, I found that the indexes seemed to be missing - a point which is referenced by NodeBB themselves here

https://community.nodebb.org/topic/11299/slow-page-loading-on-digitalocean/12?_=1646060175987

When I checked /api/recent it was indeed slow - like a snail. So, at their suggestion, I opened up mongodb and added the missing indexes
db.objects.createIndex({ _key: 1, score: -1 }, { background: true }); db.objects.createIndex({ _key: 1, value: -1 }, { background: true, unique: true, sparse: true }); db.objects.createIndex({ expireAt: 1 }, { expireAfterSeconds: 0, background: true });
The difference is quite astonishing. Now it runs like the Ferrari I’ve come to love and respect ♥

Might be useful for someone else in the same boat…
undefined

NodeBB 1.19.3
Scheduled Pinned Locked Moved Solved Performance nodebb 1.19.3 performance
33

4 Votes

33 Posts

1k Views

undefined

@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

Sudonix

NodeBB v3.0.0-rc.1

Individual Categories