WARNING: this article is obsoleted. Please refer to http://nginx.org/en/docs/ for the latest official documentation.
Controls how Nginx deals with connections.
Syntax: accept_mutex [ on | off ]
nginx uses accept mutex to serialize accept() syscalls.
Syntax: accept_mutex_delay Nms;
If a worker process does not have accept mutex it will try to aquire it at least after this delay. By default delay is 500ms.
Syntax: debug_connection [ip | CIDR]
Since 0.3.54 this option support CIDR address format
This option gives you the ability to write debug log only for the clients of this IP/NET.
Several different directives are possible.
These directives specify how many events may be passed to/from kernel, using appropriate method.
devpoll values are 32, the rest are 512.
Syntax: multi_accept [ on | off ]
multi_accept tries to accept() as many connections as possible after nginx gets notification about a new connection.
nginx uses two signals when the
rtsig method is used. The directive specified the first signal number. The second is plus 1.
rtsig_signo is SIGRTMIN+10 (40).
These directives specifies how to handle rtsig queue overflows. When overflow occurred nginx flushes rtsig queue, then it handles events switching between poll() and rtsig. poll() handles consecutively all unhandled events, while rtsig periodicaly drains queue to prevent a new overflow. When overflow is handled completely, nginx switches to rtsig method again.
The rtsig_overflow_events specifies the number of events to be passed via poll(). The default is 16.
The rtsig_overflow_test specifies after which number of events handled by poll() nginx will drains rtsig queue. The default is 32.
The rtsig_overflow_threshold works in Linux 2.4.x only. Before to drain rtsig queue nginx looks in a kernel how the queue is filled up
The default is 1/10. "rtsig_overflow_threshold 3" means 1/3.
Syntax: use [ kqueue | rtsig | epoll | /dev/poll | select | poll | eventport ]
If you have more than one event-model specified at the
./configure script, then you can tell nginx which one do you want to use. By default nginx looks for the most suitable method for your OS at
You can see the available event-models and how you can activate it at the
./configure state here
Syntax: worker_connections number
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
In a reverse proxy situation, max clients becomes
max clients = worker_processes * worker_connections/4
Since a browser opens 2 connections by default to a server and nginx uses the fds (file descriptors) from the same pool to connect to the upstream backend