@PitaJ Cool! If the query string only changes on ./nodebb build then "Cache everything" works well. I thought the query string was different for each user or represented some token/cookie. I guess I should have checked how it is generated before posting.
NodeBB high CPU Load
So as most of you know I run a site with relatively high traffic / concurrent amount of connections.
Actually I even hit over 1200 concurrent connections last week and still do so very frequently.
While my front page (Ghost) performs just fine even with one process, NodeBB causes me problems.
Very often the server returns a 500 error, simply because the load is too high.
RAM does not seems to be an issue at all compared to the CPU.
Even though I run 4 processes of NodeBB it still returns these errors.
I currently use NodeJS 5.1. My database runs on Redis.
Additionally I use NGINX to serve static files and proxy NodeBB.
Do you use plugins? If yes, list them.
I assume, Ghost performs less calculations/operations than NodeBB.
You didn't specify NodeBB version
@Nicolas my bad. I use 0.9.1 on 0.9.x (stable) branch.
- Canned Responses
- Google SSO
- Facebook SSO
- Twitter SSO
- Google AdSense
To be honest the problem already existed in previous releases without some of these plugins.
I adjusted some of my NGINX rules now though and it seems to be slightly better.
Were your nginx tweaks custom to your setup or general enough for anybody to learn from/use, @AOKP ?
@AtonB117 basically they should be common enough. However that still wasn't the actual solution of the problem.
I resolved the failure of additional caching, done by PageSpeed.
@AOKP okay, will keep an eye on CPU load...