@Dravere thx for the reply. Sadly it couldn't be more true.
The reason why I chose this setup (for now, certainly won't stick around as I hate it) is because I have a Plesk installed to manage the standard websites on the server. Plesk comes with Apache and (at least in my plesk version) can put an nginx in front as a reverse proxy to all its features. Sadly the version that it brings with itself is an nginx < 1.3.13 as would be required for nodebb to be usable as a reverse proxy.
I have tried manually updating nginx but, as Plesk brings its own custom repo to pull its own images from, this is non-trivial and has rendered my setup unusable until it was reset. So currently I am stuck with Apache until I can get that figured out
The only solution I could think of right now is to put a small machine in place that works as a sole loadbalancer and reverse proxy to which all domains point in the first place. That one can then distribute requests to the real server. That would enable me to run an additional nginx (not the plesk one) on a "non-80" port, allowing me to use any nginx. But as this is a sideproject that doesnt generate any income yet, putting a machine in front is not a viable option
The Server is running on full SSDs. I would need to ask them which ones specifically are being used if it's of relevance. I figured "as long as it's SSD, it should be fine" up until now. Let me know if I should inquire and I will.
Thanks again for your time. Cheers!
Every time I restart nodebb, the site will down for about 3 minutes. At first I doubted that the nodebb may have some thing to initialize.
Then I found that even if if restart nginx(not reload), this issue may also occur.
During this 3 minutes, the mongodb and 3 node process eat 100% CPU and most of the memory. The 3 minutes depends on the machine, 2core-4G machine will take 3 minutes and 4core-8G machine will take 1 minutes.
I wonder what was nodebb doing during that time?
@sanatisharif said in nodebb slows down:
I don't know, please tell me how can I know that?
this will give you a bunch of statistics about the system, including that's running and how much CPU it is taking.
to find out how many processes of nodejs are running i would recommend using
#> ps aux |grep node
this will spit our information about all processes that have "node" in their command line. you'll probably get a few false positives but you should be able to identify how many of those are nodebb easily enough.