Nginx server for some optimizations that easily break through 100,000 concurrent

Optimizations in Nginx directives (configuration files)

Nginx number of processes, it is recommended to be specified according to the number of CPUs, generally a multiple of it.

Allocate CPUs for each process, in the example above, 8 processes are allocated to 8 CPUs, of course you can write multiple, or a process is assigned to multiple CPUs.

This instruction is when a nginx process opens the maximum number of file descriptors, the theoretical value should be the maximum number of open files (ulimit-n) and the number of nginx process, but the Nginx allocation request is not so uniform, so it is best to be consistent with the value of ulimit-n.

Using the Epoll I/O model, needless to say.

The maximum number of connections allowed per process, in theory, the max number of connections per Nginx server is worker_processes*worker_connections.

KeepAlive timeout time.

Client requests the size of the head buffer, this can be based on your system paging size to set, the general one requested head size will not exceed 1k, but because the general system paging is greater than 1k, so this is set to paging size. The paging size can be obtained using the command getconf pagesize.

This will specify caching for open files, which are not enabled by default, max Specifies the number of caches, and the recommended number of files is the same, inactive refers to how long the file has not been requested to delete the cache.

This refers to how long it is to check the cache for valid information.

The minimum number of times a file is used in a inactive parameter in the open_file_cache instruction, and if this number is exceeded, the file descriptor is always open in the cache, as in the example above, if a file is not used once in inactive time, it will be removed.