Nginx load balancing multiple policy configurations to optimize website performance

Nginx load balancing multiple policy configurations to optimize website performance

Overview:
With the rapid development of the Internet, the number of visits to the website is also increasing. In order to meet the needs of users and improve the availability and performance of the website, we can use load balancing to share the load pressure of the server. Nginx is a high-performance web server and reverse proxy server. It provides a variety of load balancing strategies for us to choose from. This article will introduce several Nginx load balancing strategy configurations, with code examples.

1. Round Robin strategy:
   Round Robin is one of the most common load balancing strategies and is also the default strategy of Nginx. It evenly distributes requests to multiple servers on the backend, and each request is distributed to different servers in sequence. When a server goes down, Nginx will automatically exclude it from the load balancing range. The Nginx configuration of the polling strategy is as follows:

http {
    upstream backend {
        server 192.168.1.1;
        server 192.168.1.2;
        server 192.168.1.3;
    }
    
    server {
        listen       80;
        server_name  example.com;
        
        location / {
            proxy_pass http://backend;
        }
    }
}

2. Least Connections strategy:
   The Least Connections strategy will send the request to the server with the smallest number of current connections to achieve Load balancing. This ensures that the number of connections on each server is relatively balanced and avoids excessive pressure on a certain server. Nginx provides a module least_conn to implement the least connection strategy. The configuration method is as follows:

http {
    upstream backend {
        least_conn;
        server 192.168.1.1;
        server 192.168.1.2;
        server 192.168.1.3;
    }
    
    server {
        listen       80;
        server_name  example.com;
        
        location / {
            proxy_pass http://backend;
        }
    }
}

3. IP Hash (IP Hash) policy:
   The IP hash policy will distribute requests to the back-end server based on the client's IP address. This ensures that requests from the same client will be sent to the same back-end server, improving the cache effect. Nginx provides a module ip_hash to implement IP hashing strategy. The configuration method is as follows:

http {
    upstream backend {
        ip_hash;
        server 192.168.1.1;
        server 192.168.1.2;
        server 192.168.1.3;
    }
    
    server {
        listen       80;
        server_name  example.com;
        
        location / {
            proxy_pass http://backend;
        }
    }
}

4. Weighted Round Robin strategy:
   The weighted round Robin strategy allows different weights to be set for different servers. The higher the weight of the server, The greater the probability of being selected. This can effectively distribute the load pressure of the server. The configuration method of Nginx is as follows:

http {
    upstream backend {
        server 192.168.1.1 weight=3;
        server 192.168.1.2 weight=2;
        server 192.168.1.3 weight=1;
    }
    
    server {
        listen       80;
        server_name  example.com;
        
        location / {
            proxy_pass http://backend;
        }
    }
}

Summary:
By reasonably selecting and configuring load balancing strategies, we can optimize the performance of the website and improve the user's access experience. As a high-performance web server and reverse proxy server, Nginx provides a variety of load balancing strategies for us to choose from. This article introduces several common strategies such as polling, least connections, IP hashing and weighted polling, and provides corresponding Nginx configuration examples. I hope this article can be helpful to everyone's study and work.

The above is the detailed content of Nginx load balancing multiple policy configurations to optimize website performance. For more information, please follow other related articles on the PHP Chinese website!