Nginx(事件驅動反向代理)+ Node.js(事件驅動非阻塞 I/O)完美契合,輕鬆突破 Apache C10K 瓶頸。
net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_fin_timeout = 15
net.core.somaxconn = 4096
net.core.netdev_max_backlog = 4096
net.ipv4.tcp_max_syn_backlog = 20480
net.ipv4.tcp_max_tw_buckets = 400000
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
vm.min_free_kbytes = 65536
執行 sysctl -p 生效。關鍵參數解讀:
ip_local_port_range:擴大可用端口範圍,防止端口耗盡tcp_tw_reuse:快速回收 TIME_WAIT 連接tcp_fin_timeout:縮短 TIME_WAIT 等待時間somaxconn:提高監聽隊列長度upstream backend_nodejs {
server nodejs-3:5016 max_fails=0 fail_timeout=10s;
server nodejs-4:5016 max_fails=0 fail_timeout=10s;
keepalive 512; # 關鍵:啟用上游長連接池
}
server {
listen 80;
server_name api.example.com;
keepalive_timeout 10; # 客戶端保持連接
location / {
proxy_http_version 1.1; # 必須 1.1 支援 keepalive
proxy_set_header Connection ""; # 清除 Connection 頭
proxy_pass https://backend_nodejs;
proxy_next_upstream error timeout http_500 http_502 http_503 http_504;
}
access_log off; # 高負載下關閉訪問日誌
error_log /dev/null crit;
}
效果:啟用 keepalive 後,TCP 連接數降低 90%,吞吐量大幅提升。
cluster 模組或 PM2 開啟多進程利用多核pm2 start app.js -i max --name "my-api" --max-memory-restart 500M
# -i max 自動根據核心數啟動進程