@PitaJ no, with a simple ./nodebb start
But even tho, 9 req per second with just 100 concurrency seem pretty odd, what results are u having on a fresh nodebb setup?
Even with reverse nginx proxy ( no cache allowed ).
Now with nginx:
Benchmark result
wrk -t12 -c100 -d10s http://nodebb.dev
Running 10s test @ http://nodebb.dev
12 threads and 100 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 1.11s 420.12ms 1.56s 81.53%
Req/Sec 11.11 10.52 60.00 91.09%
823 requests in 10.02s, 13.84MB read
Non-2xx or 3xx responses: 139
Requests/sec: 82.16
Transfer/sec: 1.38MB
NodeBB config
{
"url": "http://localhost",
"port": ["4567", "4568", "4569"],
"secret": "thesupersecretwhichisnotasecret",
"database": "redis",
"redis": {
"host": "127.0.0.1",
"port": "6379",
"password": "",
"database": "1"
}
}
Nginx config:
upstream io_nodes {
ip_hash;
server 127.0.0.1:4567;
server 127.0.0.1:4568;
server 127.0.0.1:4569;
}
server {
listen 80;
server_name nodebb.dev;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_redirect off;
# Socket.io Support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
gzip on;
gzip_min_length 1000;
gzip_proxied off;
gzip_types text/plain application/xml application/x-javascript text/css application/json;
location @nodebb {
proxy_pass http://io_nodes;
}
location ~ ^/(images|sounds|templates|uploads|vendor|src\/modules|nodebb\.min\.js|stylesheet\.css|admin\.css) {
root /var/www/NodeBB/public/;
try_files $uri $uri/ @nodebb;
}
location / {
proxy_pass http://io_nodes;
}
}
Would be really nice if you guys could share your benchmarks, ( this is on homepage, with default setup ). no extra content