Skip to content

Instantly share code, notes, and snippets.

@kumaraswins

kumaraswins/Process and connections, web server

Last active May 31, 2019 23:55
Show Gist options
  • Save kumaraswins/d7b5554c7079113f08e0fdf38401e055 to your computer and use it in GitHub Desktop.
Save kumaraswins/d7b5554c7079113f08e0fdf38401e055 to your computer and use it in GitHub Desktop.
Download ZIP
Nginx
Raw
Process and connections, web server
worker_processes
A worker process is a single-threaded process.
If Nginx is doing CPU-intensive work such as SSL or gzipping and you have 2 or more CPUs/cores,
then you may set worker_processes to be equal to the number of CPUs or cores.
If you are serving a lot of static files and the total size of the files is bigger than the available memory,
then you may increase worker_processes to fully utilize disk bandwidth.
The worker_connections and worker_processes from the main section allows you to calculate max clients you can handle:
max clients = worker_processes * worker_connections
worker_connections is the number of simultaneous connections; so they are simply stating how to calculate, for example:
you are only running 1 process with 512 connections, you will only be able to serve 512 clients.
If 2 processes with 512 connections each, you will be able to handle 2x512=1024 clients.
The number of connections is limited by the maximum number of open files (RLIMIT_NOFILE) on your system
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment