How to optimize Nginx high concurrency kernel
What is high concurrency
The default Linux kernel parameters consider the most common scenarios and are not suitable for web applications that support high concurrent access. server, so you need to modify the Linux kernel parameters, so that nginx can have higher performance; To make adjustments, when nginx is used as a static web content server, a reverse proxy, or a server that provides a compression server, the adjustments to the kernel parameters are different. Here are the most common TCP network parameters that enable nginx to support more concurrent requests. Make simple configurations;
These require modifying /etc/sysctl.conf to change the kernel parameters.
- Configuration method
Configuration detailed analysis
#Indicates that a single process is large The number of handles that can be opened; the fs.file-max = 999999
net.ipv4.tcp_tw_reuse = 1
#When keepalive is started, the frequency of tcp sending keepalive messages; the default is 2 hours, setting it to 10 minutes can clean up invalid links faster.
ner.ipv4.tcp_keepalive_time = 600
#When the server actively closes the link, the maximum time the socket remains in the fin_wait_2 state
net.ipv4.tcp_fin_timeout = 30
#This parameter indicates the maximum value of the number of time_wait sockets allowed by the operating system. If it exceeds With this number, the time_wait socket will be cleared immediately and a warning message will be printed.
#This parameter defaults to 180000. Too many time_wait sockets will slow down the web server.net.ipv4.tcp_max_tw_buckets = 5000
#Define the value range of the local port for udp and tcp links.
net.ipv4.ip_local_port_range = 1024 65000
# Defines the minimum value, default value, and maximum value for tcp to accept cache.
net.ipv4.tcp_rmem = 10240 87380 12582912
#Define the minimum value, default value and maximum value of tcp send cache.
net.ipv4.tcp_wmem = 10240 87380 12582912
#When the network card receives data packets faster than the kernel processing speed, there will be a queue to save these data packets. This parameter represents the maximum value of the queue.
net.core.netdev_max_backlog = 8096
#Indicates that the kernel socket accepts the default size of the buffer area.
net.core.rmem_default = 6291456
# indicates the default size of the kernel socket send buffer.
net.core.wmem_default = 6291456
#Indicates that the kernel socket accepts a larger buffer size.
net.core.rmem_max = 12582912
#Indicates the larger size of the kernel socket send buffer.
net.core.wmem_max = 12582912
Note: The above four configurations need to be comprehensively considered based on business logic and actual hardware costs;
# has nothing to do with performance. Used to solve tcp syn***.
net.ipv4.tcp_syncookies = 1
#This parameter indicates the maximum length of the syn request queue accepted during the TCP three-way handshake establishment phase. The default is 1024. Setting it larger can prevent Linux from being too busy to accept new connections when nginx is busy. Lost client-initiated link request.
net.ipv4.tcp_max_syn_backlog = 8192
#This parameter is used to set and enable timewait fast recycling.
net.ipv4.tcp_tw_recycle = 1
The default value of the option is 128. This parameter is used to adjust the number of TCP connections initiated by the system at the same time. In high-concurrency requests, the default value may cause the link to time out or retransmit, so it needs to be combined with high concurrency. Adjust this value based on the number of requests. The
net.core.somaxconn=262114
# option is used to set the maximum number of tcp sockets in the system that are not associated with any user file handle. If this number is exceeded, the orphan link will be reset immediately and a warning message will be output. This limit indicates that in order to prevent simple dos***, you do not need to rely too much on this limit or even reduce this value. In more cases, increase this value.
net.ipv4.tcp_max_orphans=262114
For ease of use, you can copy it directly below
net.ipv4.tcp_tw_reuse = 1 fs.file-max = 999999 net.ipv4.tcp_fin_timeout = 30 ner.ipv4.tcp_keepalive_time = 600
The above is the detailed content of How to optimize Nginx high concurrency kernel. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

Docker container startup steps: Pull the container image: Run "docker pull [mirror name]". Create a container: Use "docker create [options] [mirror name] [commands and parameters]". Start the container: Execute "docker start [Container name or ID]". Check container status: Verify that the container is running with "docker ps".

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Create a container in Docker: 1. Pull the image: docker pull [mirror name] 2. Create a container: docker run [Options] [mirror name] [Command] 3. Start the container: docker start [Container name]

The methods that can query the Nginx version are: use the nginx -v command; view the version directive in the nginx.conf file; open the Nginx error page and view the page title.

How to configure an Nginx domain name on a cloud server: Create an A record pointing to the public IP address of the cloud server. Add virtual host blocks in the Nginx configuration file, specifying the listening port, domain name, and website root directory. Restart Nginx to apply the changes. Access the domain name test configuration. Other notes: Install the SSL certificate to enable HTTPS, ensure that the firewall allows port 80 traffic, and wait for DNS resolution to take effect.

When the Nginx server goes down, you can perform the following troubleshooting steps: Check that the nginx process is running. View the error log for error messages. Check the syntax of nginx configuration. Make sure nginx has the permissions you need to access the file. Check file descriptor to open limits. Confirm that nginx is listening on the correct port. Add firewall rules to allow nginx traffic. Check reverse proxy settings, including backend server availability. For further assistance, please contact technical support.
