You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
net.core.somaxconn – The maximum number of connections that can be queued for acceptance by NGINX. The default is often very low and that’s usually acceptable because NGINX accepts connections very quickly, but it can be worth increasing it if your website experiences heavy traffic. If error messages in the kernel log indicate that the value is too small, increase it until the errors stop.
Note: If you set this to a value greater than 512, change the backlog parameter to the NGINX listen directive to match.
And there are more info about rate-limiting on the page. Also quoted here: #843 (comment)
That setting doesn't increase performance, it only expands the connection queue so that fewer connections will be rejected. This is mostly useful if you have many short-lived connections, probably less so for our websocket-based API.
Learnt one more trick to improve
performanceresponse time for API nodes (do it before starting a node):Need to document this somewhere.
Benchmark data is welcomed.
//Update:
According to https://www.nginx.com/blog/tuning-nginx/:
And there are more info about rate-limiting on the page. Also quoted here: #843 (comment)
More info: https://steemit.com/witness-category/@someguy123/guide-optimise-your-rpc-server-for-better-performance
The text was updated successfully, but these errors were encountered: