Why is nginx so fast?
The main reason is that Nginx uses the latest epoll (Linux 2.6 kernel) and kqueue (freebsd) network I/O model.
epoll is a method of multiplexing IO (I/O Multiplexing), but it is only used for Linux2.6 and above kernels. Before we start discussing this issue, let us first explain why. Multiplexing IO is required.
Let’s explain with an example in life.
Suppose you are studying in college and have to wait for a friend to visit, and this friend only knows that you are at No. A Building, but I don’t know where you live specifically, so you made an appointment to meet at the door of Building A.
If you use the blocking IO model to deal with this problem, then you can only wait at Building A all the time. Waiting for the arrival of your friends at the door of Building No. 1. During this time, you cannot do anything else. It is not difficult to know that the efficiency of this method is low.
Now times have changed, and multiplexing has begun to be used. The IO model is used to deal with this problem. You tell your friend to come to Building A and ask the building manager to tell you how to go. The building manager here plays the role of multiplexed IO.
Further explain the difference between the select and epoll models.
The select version of the aunt does the following: For example, when classmate A’s friend comes, the select version of the aunt is stupid, and she takes her friends from room to room to check who is who. It’s classmate A. The friend you were waiting for has arrived, so in the actual code, the select version of the aunt does the following:
##int n = select(&readset,NULL,NULL,100);
for (int i = 0 ; n > 0; i) {
if (FD_ISSET(fdarray[i], &readset)){
do_something( fdarray[i]);
--n;
}
}
n
=epoll_wait(epfd,events,20,500);
for
(i=0;i<n; i){do_something(events[n]) ;}
In epoll, the key data structure epoll_event is defined as follows:
typedef union epoll_data {
void * ptr;
int fd;__uint32_t u32;
__uint64_t u64;
} epoll_data_t;
struct epoll_event {__uint32_t events;
/* Epoll events */epoll_data_t data ;
/* User data variable */};
Don’t underestimate these efficiency improvements. In a large-scale concurrent server, polling IO is one of the most time-consuming operations. Going back to the example, if every A friend's building manager wants to query the classmates in the whole building, so the processing efficiency will inevitably be low. Soon there will be a lot of people on the floor.
Compare the earliest blocking IO processing model , it can be seen that after using multiplexed IO, the program can freely perform its own work except IO operations. Only when the IO status changes, multiplexed IO will notify it, and then take corresponding operations. , instead of having to block and wait for the IO status to change.
It can also be seen from the above analysis that the improvement of epoll over select is actually a specific application of the idea of exchanging space for time.
For more Nginx related technical articles, please visit the Nginx Tutorial column to learn!
The above is the detailed content of Why is nginx so fast?. 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.

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".

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).

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.
