Question

What is the maximum nginx worker_connections I can set for my droplet?

I have a NodeJS API running on a 4GB Memory and 2 Core CPU Standard Droplets. The API has real time functionalities using Socket.io and is serving around 500 concurrent users.

Lately I noticed that the API sometimes stop handling any requests for like 5 - 10 seconds and then continues to work.

When I checked Nginx error logs I found this alert occurring a lot :-

[alert] 7193#7193: 768 worker_connections are not enough

Could this be the issue making the API miss some requests?

And how do I know what is the maximum worker_connections I can set? Currently it is set to 768


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

worker_connections is bound by worker_rlimit_nofile. So always set it to be equal or less than the value of worker_rlimit_nofile. worker_rlimit_nofile is bound by the ulimit of number of open files for the user (/etc/security/limits.conf) and is in turn limited by the kernel’s fs.file-max:

# sysctl fs.file-max
fs.file-max = 9883453