Summary of methods to improve Node.js performance

This time I will bring you a summary of methods to improve the performance of Node.js, and what are the precautions to improve the performance of Node.js. The following is a practical case, let’s take a look.

Node.js is single-threaded non-blocking I/O, allowing it to support thousands of concurrent operations. This is exactly how NGINX solves the C10K problem. Node.js is known for its efficient performance and development efficiency.

1. Implement a reverse proxy server

Node.js can handle larger amounts of network traffic more easily than most application servers, but this is not what Node.js was designed to do.

If you have a high-traffic site, the first step to improve performance is to put a reverse proxy server in front of your Node.js. This protects your Node.js server from being directly exposed to the network, and allows you to flexibly use multiple application servers for load balancing and static file caching.

Use NGINX as a reverse proxy in front of an existing server. As a core application of NGINX, it has been used in thousands of sites around the world.

Here are the advantages of using NGINX as a reverse proxy server:

Simplified permission handling and port allocation

Process static resources more efficiently

Better handling of Node.js crash situations

Mitigating the impact of DoS attacks

Note: This article explains how to use NGINX as a reverse proxy server in Ubuntu 14.04 or CentOS environment, and it is effective to use NGINX as a reverse proxy server in front of Node.js.

2. Caching static files

As traffic increases, Node-based servers begin to show pressure. At this time, you may want to do two things:

Use more Node.js servers.

Load balancing among multiple servers

This is actually very simple. NGINX is implemented as a reverse proxy server from the beginning, which makes it easy to do caching and load balancing.

The Modulus website has a useful article that introduces the performance improvement of using NGINX as a Node.js reverse proxy server. Only use Node.js At the time, the author's website could handle 900 requests per second. After using NGINX as a reverse proxy server to process static files, the website can handle more than 1600 per second requests, nearly twice the performance improvement.

The following is the configuration code for the website to improve the performance mentioned above:

nginx
server {
listen 80;
server_name static-test-47242.onmodulus.net;
root /mnt/app;
index index.html index.htm;
loction /static/ {
try_files $uri $uri/ =404;
}
location /api/ {
proxy_pass http://node-test-45750.onmodulus.net;
}

3. Implement Node.js load balancing

The end goal — Node.js runs multiple application servers and balances load among them.

It is more difficult to implement load balancing in Node.js because Node.js allows browser-side JavaScript and server-side Node.js to pass json is used for data interaction, which means that the same client can repeatedly access a specific application server, and it is also difficult to share session between multiple application servers.

How NGINX implements stateless load balancing:

Round Robin. New requests go to the next server in the list

Least Connections. New requests go to the server with the least number of connections

IP Hash. Specify the server based on the hash value of the client IP

Only IP Hash can benefit Node.js application servers as a way to reliably proxy client requests to the same server.

4. Proxy WebSocket connection

All versions of HTTP are designed for clients to actively request servers, while WebSocket can enable servers to actively push messages to clients.

The WebSocket protocol makes stable interaction between client and server easier, while also providing smaller interaction latency. When you need a full-duplex communication, that is, both the client and the server can actively initiate message requests when needed, then use WebSocket.

The WebSocket protocol has a sound JavaScript interface, so it is also natively suitable for using Node.js as an application server. As the number of connections increases, it makes sense to use NGINX as a proxy on the client and Node.js server for caching static files and load balancing.

5. Implement SSL/TLS and HTTP/2

More and more websites use SSL/TLS to ensure the security of information exchange. You may also consider whether to add it to your website, but if you decide to do it, NGINX has two ways to support it:

You can use NGINX as an SSL/TLS reverse proxy, where the Node.js server uses the decrypted request and returns the unencrypted content to NGINX.

Using HTTP/2 can offset the performance overhead caused by SSL/TLS. NGINX supports HTTP/2, so you can use both HTTP/2 and SSL to proxy requests without making any changes to your Node.js server.

During the implementation phase you need to update the URL in the Node.js config file to use SPDY or HTTP/2 in your NGINX configuration file Optimize connections. Adding HTTP/2 support means that browsers that support HTTP/2 can use the new protocol to interact with your application, while older browsers continue to use HTTP/1.x.

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!

Recommended reading:

The above is the detailed content of Summary of methods to improve Node.js performance. For more information, please follow other related articles on the PHP Chinese website!