Ulimit on 2G droplet = 1024. Should I change it ?


I was just reading this post : , which states the number of worker processes for NGINX can be calculated by multiplying the number of CPU’s with the number that comes out of ulimit -n … this command gives me 1024.

Since I have 2 cores that would be :

worker_processes : 2 (or auto) worker_connections : 1024 (or would that be 2048?)

For the sake of it : why is it that I get 1024 on a 512MB droplet, while I also get 1024 on a 2G droplet ?

I’d like to know the following : should I try to set this limit higher for optimal performance ? If yes, how high should I set it, and how do I do this (in regard of ulimit) ? I am running an PHP app on this droplet that tracks clicks (and redirects to other pages) … It somehow doesn’t make sens to have the same worker_connections on a 2G droplet as on a 512MB droplet …

I might be wrong, so that’s why I’m asking …

Thanks in advance, Lex


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

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.

Both servers have the same number of cores, so leaving them both set to 1024 is advisable.