Why tuning handles high traffic in Nginx - Why It Works

Introduction

When many users visit a website at the same time, the server can slow down or crash. Tuning the server settings helps it handle many visitors smoothly without delays or errors.

When your website gets slow during busy hours and you want faster responses.

When you expect a big event that will bring many visitors to your site at once.

When your server crashes or refuses connections because too many users try to connect.

When you want to improve user experience by reducing waiting time on your website.

When you want to use your server resources efficiently without wasting memory or CPU.

Config File - nginx.conf

nginx.conf

worker_processes auto;
events {
    worker_connections 1024;
    multi_accept on;
}
http {
    keepalive_timeout 65;
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    server {
        listen 80;
        server_name example.com;
        location / {
            root /usr/share/nginx/html;
            index index.html index.htm;
        }
    }
}

worker_processes auto; lets Nginx use all CPU cores for better performance.

worker_connections 1024; sets how many users each worker can handle at once.

multi_accept on; allows workers to accept multiple connections quickly.

keepalive_timeout 65; keeps connections open briefly to speed up repeated requests.

sendfile, tcp_nopush, tcp_nodelay; optimize how data is sent to users for faster delivery.

Commands

This command checks if the Nginx configuration file is correct before restarting the server.

Terminal

sudo nginx -t

Expected Output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

This command restarts Nginx to apply the new tuning settings so they take effect.

Terminal

sudo systemctl restart nginx

Expected Output

No output (command runs silently)

This command checks if Nginx is running properly after the restart.

Terminal

sudo systemctl status nginx

Expected Output

● nginx.service - A high performance web server and a reverse proxy server

   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)

   Active: active (running) since Fri 2024-06-14 10:00:00 UTC; 5s ago

 Main PID: 1234 (nginx)

    Tasks: 3 (limit: 1152)

   Memory: 5.0M

   CGroup: /system.slice/nginx.service

           ├─1234 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;

           ├─1235 nginx: worker process

           └─1236 nginx: worker process

This command counts how many active connections are currently open on port 80 to see if the server handles many users.

Terminal

netstat -an | grep ':80' | grep ESTABLISHED | wc -l

Expected Output

45

Key Concept

If you remember nothing else from this pattern, remember: tuning Nginx settings lets your server handle many users smoothly without slowing down or crashing.

Common Mistakes

Changing worker_connections to a very low number like 10

This limits how many users can connect at once, causing slowdowns or refused connections under high traffic.

Set worker_connections to a higher number like 1024 or more depending on your server capacity.

Not testing the configuration with 'nginx -t' before restarting

If there is a syntax error, Nginx will fail to restart and your website will go down.

Always run 'sudo nginx -t' to check for errors before restarting.

Restarting Nginx without applying tuning changes

Restarting without changes does not improve performance and wastes time.

Edit the config file first, then test and restart to apply tuning.

Summary

Edit nginx.conf to increase worker_processes and worker_connections for better traffic handling.

Test the configuration with 'sudo nginx -t' to avoid errors.

Restart Nginx with 'sudo systemctl restart nginx' to apply changes.

Check active connections to monitor server load.